The Lean Canvas: one page for an idea whose problem is not proven yet
Run this method in IdeaHone
Creates a space with the entities and scoring criteria of this method, ready for your next session.
Most new ideas do not fail because the team could not build them. They fail because the problem was smaller than everyone thought, or belonged to someone who would not pay to have it solved. The Lean Canvas puts that risk on the page. Ash Maurya adapted it from the Business Model Canvas in 2010 for start-ups and new ventures, and described it in his book Running Lean. It keeps the one-page format but swaps four blocks for the questions that matter most when the problem itself is still a guess.
How it differs from the Business Model Canvas
The Business Model Canvas describes how an established business works: partners, activities, resources, relationships. For an early idea, most of those answers are not known yet and not the main risk. The Lean Canvas replaces them.
| Business Model Canvas | Lean Canvas | Why |
|---|---|---|
| Key partners | Problem | Without a real problem, partners do not matter yet |
| Key activities | Solution | The smallest thing that solves the problem |
| Key resources | Key metrics | The few numbers that show it is working |
| Customer relationships | Unfair advantage | What others cannot easily copy or buy |
Filling it in, in the right order
The order matters more than on most canvases. Each block builds on the one before, and the later blocks are pointless if the first ones are wrong.
- Customer segments. Who has the problem? Name the early adopters: the people who have it most and are already trying to solve it. "Store managers who order for two stores" beats "retailers".
- Problem. The top one to three problems of that segment, and the existing alternatives: how they solve it today. If you cannot name an alternative, check whether the problem is real.
- Unique value proposition. One clear sentence: why your answer is different and worth attention. Write it for the early adopter, not for everyone.
- Solution. The simplest answer to each problem. Keep it short; this is the block teams love most and should spend least time on.
- Channels. How you reach the early adopters, especially the first hundred.
- Revenue streams. What you charge, how, and from whom. A price is an assumption like any other.
- Cost structure. What it costs to reach customers and deliver the solution, including people and time.
- Key metrics. The few numbers that show progress. Not page views: the action that shows the problem is real, such as a repeat order.
- Unfair advantage. What cannot be copied or bought easily: inside knowledge, a community, a channel nobody else has. Most early canvases leave this block empty, and that is honest.
Fill in the canvas in 20 minutes, alone or in pairs, before anyone discusses it. A fast first version shows where the team has guesses and where it has evidence. A slow, polished one hides the difference.
From canvas to test
A filled Lean Canvas is a list of assumptions. The riskiest one is usually in the first three blocks: that this segment has this problem badly enough to change what they do. Mark the riskiest notes, put them on an assumption map, and design a test for the top one with experiment design. Set a kill criterion before the test starts, so the result decides and not the mood in the room. Then update the canvas. A canvas that has not changed after a few weeks of tests has not been used.
Where Lean Canvases go wrong
- Solution first. Teams that start with the solution then pick a problem to match it. Start with the customer and the problem.
- Everyone as the segment. "Small businesses" is not a segment. If you cannot name ten people who belong to it, it is too wide.
- No existing alternatives. Every real problem has a workaround, even a bad one. Without it you do not know what you are competing with.
- Vanity metrics. Sign-ups and clicks rise easily. Pick the metric that would hurt to see fall.
- An invented unfair advantage. "First mover" and "great team" are not advantages others cannot copy. Leave the block open until you have one.
The Lean Canvas was created by Ash Maurya (leanstack.com) as an adaptation of the Business Model Canvas, and is licensed under CC BY-SA 3.0. IdeaHone's Lean Canvas tool shows this credit on the canvas and in every export.
Run the workshop. IdeaHone keeps the record.
While you facilitate, IdeaHone turns what is said into ideas, questions and decisions on a shared board, with who said it. Nobody writes the minutes afterwards.
What is the Lean Canvas?
A one-page business model template for new ideas and start-ups, adapted by Ash Maurya from the Business Model Canvas. Its nine blocks are customer segments, problem, unique value proposition, solution, channels, revenue streams, cost structure, key metrics and unfair advantage.
When should I use the Lean Canvas instead of the Business Model Canvas?
When the problem and the customer are still unproven, which is true of most new ideas. The Business Model Canvas fits better when the customer side is known and the question is how to deliver: partners, activities and resources.
In which order do you fill in the Lean Canvas?
Customer segments, problem, unique value proposition, solution, channels, revenue streams, cost structure, key metrics and unfair advantage. Start with who has the problem, and leave the unfair advantage for last.
What is an unfair advantage?
Something that helps you and cannot easily be copied or bought by others, such as inside knowledge, an existing community or an exclusive channel. Most early ideas do not have one yet, and an empty block is better than an invented one.
