Lean Startup
Build-measure-learn loop
Lean Startup is a methodology for building products under conditions of extreme uncertainty. Its core loop — Build → Measure → Learn — emphasises validated learning over building to spec. The goal is to test hypotheses about customers and business models as quickly and cheaply as possible, using MVPs and experiments rather than full product launches.
Developed by Eric Ries, published in 'The Lean Startup' (2011). Draws on lean manufacturing principles and Steve Blank's customer development methodology.
Use Lean Startup when
- ✓Early-stage product development where the problem or solution is unproven
- ✓You're exploring a new market, customer segment, or business model
- ✓The team is prone to building without validating customer demand first
- ✓You need a framework for prioritising experiments over features
Avoid it when
- ✗You're in scale mode with a proven product — the uncertainty is operational, not conceptual
- ✗Regulatory or safety constraints make rapid experimentation impossible
- ✗Stakeholders interpret "MVP" as "low quality" rather than "minimum viable hypothesis test"
Key Concepts
The smallest experiment that tests a specific hypothesis. Not a buggy v1 — a deliberate learning vehicle.
Learning backed by real data from real customers. Distinguishes itself from assumptions, opinions, and vanity metrics.
A structured course correction — changing one element of the business model based on validated learning.
Measuring progress by learning milestones rather than vanity metrics (pageviews, registrations).
The core belief about customers or market that the entire business model depends on. Test this first.
Measuring customer behaviour by acquisition cohort to see if learning is actually improving the product.
How it works
Create the smallest possible artifact that tests your leap-of-faith assumption. Could be a landing page, a prototype, a concierge service, or a wizard-of-oz test.
Define actionable metrics before building. Measure behaviour, not just opinions. Use cohort analysis to separate signal from noise.
Decide: persevere (double down on what's working) or pivot (change the hypothesis and run a new experiment). The learning must be validated — not just 'we think we understand better now.'
Tools that support Lean Startup
Industry standard for software development teams — most PMs will encounter Jira in their career
Exceptionally intuitive and visually clean interface — one of the lowest onboarding friction tools for non-technical teams
Highly visual and intuitive interface with color-coded boards — one of the easiest PM tools for non-technical teams to adopt
All-in-one platform replacing multiple tools — docs, whiteboards, goals, time tracking, chat, and project management in a single workspace
Unmatched flexibility as an all-in-one workspace — combines docs, wikis, databases, and project management in a single tool
Spreadsheet-familiar interface makes adoption easy for teams transitioning from Excel — minimal training needed for basic use
Extremely intuitive drag-and-drop Kanban interface — virtually zero learning curve, new users productive within minutes
Best-in-class infinite canvas experience — the gold standard for collaborative whiteboarding with real-time multiplayer editing
Frequently Asked Questions
A prototype tests the design or usability of a solution. An MVP tests whether customers have the problem and will pay to solve it. An MVP can be a no-code landing page, a spreadsheet, or a manual service — it doesn't have to be software.
Metrics that look good but don't help you make decisions: total signups, total pageviews, press mentions. Actionable metrics tie behaviour to decisions: activation rate, retention cohorts, revenue per cohort.