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 startuplessonslearned.com 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
Startuplessonslearned.com : Lessons Learned
Startuplessonslearned.com : Lessons Learned: Minimum Viable Product: a guide

Comments

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

Lancement de ProductTank Lyon

Tout d’abord, bonne année 2020. Je me suis investi ces dernières années dans les communautés/événements CARA Lyon, MiXiTConf, LyonDataScience et CaféDevOps sur Lyon, France. Ces activités m’ont permis de comprendre les experts de ces domaines, d’apprendre quelques notions fondamentales à travers leurs exposés et d'améliorer mes capacités d’échange avec eux. Product Manager depuis plus de 5 ans, je désire améliorer mes réflexes et compétences dans mon domaine. Le faire à travers des rencontres/meetup est ce que je préfère et j’aimerais retrouver la stimulation des communautés dans cette discipline. En cette année 2020, quelques Product Manager Lyonnais, lançons, le meetup ProductTankLyon à Lyon, France. Le réseau ProductTank compte plus de 150 meetup dans le monde et profite des conférences, blog et podcast MindTheProduct. Inscrivez-vous ici , si vous voulez vous joindre à nous.

Read bead experiment

The "Read bead experiment" was created by Dr. Edward Deming and aim to demonstrate the ineffectiveness (sometimes effectiveness) of the various management methods. At the end of the experiment, a statistical graphical tool is used to analyse the experiment's results. By following this exercise, you will understand that actions taken by the people playing the managers are detrimental to the employees, but after the analyses are shown to have no impact on the efficiency of the process . The conclusion proposes ways to properly use performance data in a quality environment in order to achieve continual improvement. The several videos by Fluor Hanford (Steve Prevette) posted below, will help you to understand what is really important in a process. Meet the  company  with its "willing workers", quality control personnel, a data recorder, and a foreman. All wish to produce white beads using a 50 holed paddle, but unfortunately there are bad quality red beads.