A UX practice that prioritizes learning over deliverables, emphasizing rapid experimentation, cross-functional collaboration, and validated assumptions. Lean UX reduces wasted design work by testing ideas quickly before committing to full implementation.
Common contexts
- Running a two-day assumption validation exercise before committing to a six-week feature build
- Replacing a lengthy UX spec document with a shared hypothesis board that engineering and product review together
- Shipping a low-fidelity prototype to beta users to test demand before designing the full UI
Use when
Use Lean UX when the team is working with high uncertainty about user needs or technical feasibility — it collapses the gap between 'we think users want this' and 'we know users want this' before significant resources are spent.
Avoid when
Don't apply Lean UX when the problem is well-defined and the solution space is narrow — in those cases, fast experimentation creates unnecessary churn and delays execution.
The hardest part of Lean UX is getting teams to value a proven-wrong hypothesis as highly as a proven-right one — both save money, but only one feels like progress.
Real-world examples
- Dropbox validated demand with a 3-minute explainer video before building any product — a canonical Lean UX 'fake door' experiment that generated 75,000 sign-up requests overnight.
- Spotify's product squads run 'assumption-mapping' workshops each quarter to surface and prioritise the riskiest product hypotheses, then design the minimum test to invalidate them before committing engineering effort.
- Intuit's 'Follow Me Home' program — sending designers to observe customers using TurboTax in their own homes — is an ethnographic Lean UX practice that has driven major simplification in each tax-year release.