practiceStrategy & discovery

Lean UX

A collaborative approach to product design that treats ideas as hypotheses, favors outcomes over deliverables, and learns through small experiments.

Download Markdown (.md)

01What it means

Lean UX, developed by Jeff Gothelf and Josh Seiden, adapts lean and agile ideas to user experience work. Cross-functional teams state assumptions and desired behavior changes, create the smallest useful experiments, and use evidence to adjust direction instead of relying on large up-front specifications.[1][2]

Assumptions converted into shared evidence Cross-functional teams build the smallest useful experiment and learn together
  1. 01FrameProblem, users, outcomes, constraints
  2. 02Expose assumptionsTurn important beliefs into hypotheses
  3. 03Choose evidenceSmallest credible experiment
  4. 04Build + observeBehavior and outcomes, not opinions alone
  5. 05Learn + decideIterate, pivot, stop, preserve necessary records

The aim is reduced uncertainty and changed outcomes, not the production of large up-front specifications.

02Why it matters

Long design phases and detailed handoffs delay feedback and make teams defensive about sunk work. Lean UX keeps design, product, and engineering involved in shared learning, reduces the cost of changing direction, and measures progress through customer and business outcomes rather than document completion.

03When to use it

Use it in cross-functional product teams facing meaningful uncertainty and able to release or test incrementally. It is helpful when handoffs dominate work or roadmaps assume untested features. Adapt it in regulated or safety-critical contexts where documentation remains essential.

04How it works

  1. Clarify the business problem, target users, outcomes, and constraints.
  2. Expose assumptions and convert important ones into testable hypotheses.
  3. Collaboratively generate options and identify the smallest evidence needed.
  4. Build prototypes, concierge services, or product increments appropriate to the risk.
  5. Observe behavior and outcomes, not only opinions.
  6. Learn together and iterate, pivot, or stop while preserving necessary records.

05A practical example

Example

A B2B analytics team believes weekly insight emails will improve return usage. Rather than fully automating reports, it manually composes a small set for consenting customers, measures opens and follow-up actions, interviews recipients, and revises the value hypothesis before engineering the system.

06Where it breaks

“Lean” can be misused to justify rushed research, low quality, or missing documentation. Small tests may miss long-term effects, accessibility needs, and systemic harms. The approach also struggles when teams lack decision authority, customer access, or reliable outcome measures.

Common mistakes

  • Equating Lean UX with skipping research or design craft.
  • Calling a backlog item a hypothesis without defining evidence or outcomes.
  • Optimizing experiment speed while ignoring participant ethics and product quality.

07Sources

  1. Lean UX: Designing Great Products with Agile TeamsJeff Gothelf and Josh Seiden · Official book siteLean UX: Designing Great Products with Agile Teams
  2. How to Use the Lean UX CanvasJeff Gothelf · Creator-authored guideHow to Use the Lean UX Canvas
View saved topics

Start typing to search titles, definitions, categories, and frameworks.