Skip to main content

Lean startups

Through Shmula, I went to the Eric Ries' You Tube channel and I watched two of his interviews done by Scobleizer: The Lean Startup, Part I/II". Eric Ries writes and has popularised the term "Lean Startups.

At the beginning of his interview Eric establishes the software context: Compared to the traditional industries, this discipline has no physical constraints. Consequently the developers' imaginations are directly translated into a real product.
Eric has ten years experience as an entrepreneur and he saw so many talented people building software that nobody wanted. So he digs the concept of Lean start-up from his research to help entrepreneurs test their ideas right from the beginning of their activity.

At the beginning of a start up, Eric would:
  • Have a vision to change the world,
  • Test elements of his vision on customers,
  • Have a Problem Team, a part of the company dedicated to understand what customers' problem they try to solve,
  • Have a solution team, the other part of the company, who try to build the "minimum valuable product".

I do agree that the Lean idea of "minimum viable product" can easily be understandable in a physical world, due to its own constraints. Because of the flexibility, nothing forces developers to face their bad habits. Software guys tend to wait, to work and wait more, to feel their bag of new stuff is big enough to launched. Great enough from their point of view usually means a lot of stuff from their own perspective, only a little of which is valuable.

Eric gave a great example about a full product delivery up to a real customer, up to the far end of the production line. He gave this example about software refactoring oriented scalability, made available in production after 3 days of work. This Just in Time way is in opposition to large batch development.
Based on an example around employees training in a start-up , he drives us to the root cause, using the 5 whys principle. These 5 questions, most of the time, push an organisation to uncover layer by layer, the path to the real problem, through either technical or management structures.

In the second part, the discussion moves to agile principles, something which we understand much more nowadays. But he really emphasises the notion of testing your vision by steps, and to make sure the new features change the behaviour of the customer.

I really enjoy listening to Eric, because he has enough experience to step back and to give us valuable feedback. 

Sources :
Shmula : The Lean Startup, Video Interview, Eric Ries, Part 1
Youtube :StartupLessonsLearne Channel
Youtube : Scobleizer Channel : Lessons Learned : Lessons Learned: Minimum Viable Product: a guide


Popular posts from this blog

Learning about Data Science?

This is the end of a beautiful summer, and also one of the warmer recorded in France. I’m continuing my journey in the product management world and today I’m living in the product marketing one too. I will blog about this later. During this first half of this year, I read several articles on big data and started to understand how important the data science discipline is. Being able to define a direction/goal to search, collecting the proper data, then using a collection of techniques to extract something others can’t see - it sounds like magic. Also, when I listened to the Udacity Linear Disgression podcast episode “Hunting the Higgs”, I understood people with these skills can be better at solving a problem than the domain experts themselves. Katie Malone explained that in a competition to solve a particle physics problem, the best results came from machine learning people. Then I read the article about Zenefit on the vision mobile website : “Zenefits is an insurance compan

Didn't register yet to the European Agile event 29-31 August in Paris?

I tell you, I’m not an expert in agile, just someone who found solution to my professional problems using agile methodologies. If you are convinced too and want to move further, please join us at the end of august, for a lot of open discussions and fun. Things are moving forward in the ALE 2016 organisation. Already, a great diversity of people answer to our call as shown below, but we need more. Yes the ALE 2016 will be great as it has always been since 2011 in Berlin. For those who do not know about the yearly ALE event, please find below a few tips. What is it?  If you do not know yet about the Agile Lean Europe event, here a few tips. ALE is a event for practitioners, meaning people who already practice agile methodologies like developers, modern CEO, teachers, leaders, etc.  Sharing ideas and solving problems are the ALE mains goals: people can propose topics where they share their experience, other can ask to solve a problem the can’t alone  The event formats helps

Unconference Agile Lean Europe 2016 (Paris) - Laissez vous porter.

No EN version yet here, sorry.  Second version. Précision du principe de communauté pour résoudre des problèmes. Ceci est un message personnel à toi qui serais dans le doute par rapport à ALE2016 . Il y a quelques semaines, j’étais à Mix-IT , une conférence de développement informatique / organisation, pour assister Yves Hanoulle dans l’animation du jeu The Scaling Ball Game . Durant les conversations hors des sessions, j’ai échangé avec différentes personnes sur le prochain événement auquel je vais participer : ALE2016 , A ma plus grande surprise, j’ai découvert qu'ALE impressionnait, faisait peur ou était incompréhensible pour ceux qui n’avaient pas encore jamais participé à cet événement. Mon message est simple : Laisse toi aller, viens à ALE2016. Durant les 5 premières premières sessions dans chaque coin de l’Europe, les remarques ont toujours été les mêmes. En repartant, tu auras : Découvert des participants qui sont tous très abordables. Tous viennent à cet évé