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
Labels:

Comments

Post a Comment

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...
5 comments
Read more

What I’m learning about AI agents

My learning journey in the world of AI, updated for 2026 Originally published in March 2025. Updated in August 2026. I started this list because I kept seeing the same terms used in different ways. I needed a simple map to understand what each technology actually does, and where it may be useful when bringing AI into a product. AI changes so quickly that a learning journey can become dated in a few months. My first version of this article was an attempt to map the technologies around AI agents and to make sense of the growing number of tools. Since then, the topic has moved from interesting experiments to real business systems. This updated version keeps the original intention: learn in public, organise the landscape, and focus on what is useful in practice. What changed since 2025 In early 2025, most conversations were still about chatbots, prompt engineering and early agent frameworks. In 2026, the more useful question is no longer "which model is the best?" but ...
Post a Comment
Read more

Embracing Bluesky: A search for authentic dialogue beyond professional networks

LinkedIn is great for professional networking, but where can you have conversations with different people on a wider range of topics? I joined Twitter in 2008, later than many of my peers. Initially, it served as a platform for personal intellectual growth, offering pleasant exchanges focused primarily on computer science, human organisation, design and product management. But the growing awareness of climate issues changed everything. Anger became the dominant tone, and I found myself missing a more constructive environment. I don't want to spend my days in a world full of anger. In search of a new wave of self-improvement and more balanced discussions, I've made the move to: https://bsky.app/profile/lookingforanswers.me  I look forward to connecting with you there for more diverse and enriching conversations.
Post a Comment
Read more