Skip to main content

What Is Lean Startup? Here's What You Need to Know

You've probably heard a lot of buzz about "lean startups".  You may wonder if it's mere hype, applies just to tiny bootstrap ventures, or if adopting some lean startup methods might actually benefit your company.


One of the top problems companies face as they make product decisions
is that the process of learning the market, and learning what makes the product successful, is slow and unreliable. Sometimes they suffer analysis paralysis, swerve from one big deal to the next, allow conventional industry wisdom to stifle innovation, or squabble over uninformed personal opinions. In other cases, they make decisions quickly but fail to learn from their inevitable mistakes until after they've invested exorbitant amounts of time and money.

If you find that your organization is facing this problem, it's worthwhile to consider lean startup methods.


Just as scientists use the scientific method to learn how the universe works, your product team can apply lean startup methods to learn what business model for your product will work in the market. Lean startup practitioners:
  1. Collect data. Practitioners observe and interview prospects to gain qualitative insights into their situations, challenges, and the ways they operate. They also examine quantitative data for further insights.
  2. Form hypotheses. Based on their observations and insights, practitioners form and capture hypotheses about the business model for their products. These hypotheses include the problems to solve, the key elements of the solution, the unique value proposition, the buyer and user personas, key metrics or user activities, costs, and revenue streams. Hypotheses may also include measurable predictions of the impact of various marketing or sales tactics.
  3. Conduct experiments. Recognizing that at least some of their initial business model hypotheses are likely to be wrong, practitioners design and run experiments to test the hypotheses. Often these experiments confront prospects with real-world choices (such as functional product) and measure how prospects behave when confronted with these choices.
  4. Learn and adjust. Having conducted experiments to test hypotheses, practitioners analyze the results and adjust their hypotheses.
These activities often occur in parallel and not necessarily in this sequence. For example, entrepreneurs commonly think of product ideas prior to formally collecting market data.

Applying these methods in an iterative or continuous fashion enables product teams to confront product strategy risks and quickly and reliably learn markets with more targeted - and ultimately, less wasteful - business investments.


Lean startup practitioners essentially apply agile methods to the entire business for a product. Most software companies have adopted at least some agile development practices. But unlike companies that iterate merely on the development of the product, lean startups iterate on the requirements, the positioning, the target markets and personas, and sales and marketing tactics.  They monitor and optimize the sales and usage funnels. They emphasize the delivery of working product and prospect-touching experiments over exhaustive planning and documentation devoid of external feedback.

Summary

Learning markets reliably and expeditiously, and learning what will make products successful, is one of the primary challenges many companies face, whether those companies are startups or large, established corporations. By applying scientific practices and agile principles across the entire business for a product, lean startup is designed to address this challenge.

How does your company currently make product decisions?  How would you know it's time to add new approaches or practices to the mix? The next blog entry will explain how you can begin to put some lean startup methods into practice right away, once your team is ready for some change.

Thanks to Koen Bosma, Ash Maurya, and Emiliano Villareal for providing helpful feedback on this blog entry, and for their thought leadership on the topic of lean startup methods.

Comments

Mike Lunt said…
It seems that #3 Experiment is where most companies drop the ball. They consider failed POCs as "wasted time", when the reality is that millions were likely saved knowing in advance of full scale development that the idea wouldn't succeed.
Roger L. Cauvin said…
Thanks, Mike.

Based on my experience and some of the executive interviews I've recently conducted, it does seem purposeful experimentation is not very common. The exception is some limited A/B testing on UI options.

A lot of companies also fall short on the collection of data through prospect interviews. "I demoed our solution, and the prospect said it was f*ckin' cool!" does not constitute reliable hypothesis validation or market learning. They make this and other typical mistakes when visiting with prospects.
Unknown said…
Nice, simple explanation.

I agree with Mike, gathering experimental data is tough and most teams don't know how to do it. Any tips?
Roger L. Cauvin said…
Thanks, Bruce. I'll have some tips on applying lean startup methods in an upcoming blog entry. Some of the tips will address purposeful experimentation and the gathering of data from experiments.

In the meantime, do you have any tips you'd like to share?

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware