Lean UX: principles, process and the think-make-check cycle

Lean UX is a way of designing digital products that replaces heavy documentation with fast experiments and shared learning. Teams state assumptions as hypotheses, build the smallest thing that tests them and use customer evidence to decide what to do next.

Jeff Gothelf and Josh Seiden set out the approach in their book Lean UX, first published in 2013. This guide covers the definition, principles, the think-make-check cycle, hypothesis statements, the Lean UX canvas and how it fits with agile sprints.

Key takeaways

Lean UX, or lean user experience design, focuses on learning from users quickly rather than producing detailed deliverables.

The core loop is think, make, check: form a hypothesis, build a small test and review the evidence.

Hypothesis statements turn design opinions into things you can test.

Design is a team activity shared with developers, product managers and others.

Lean UX fits inside agile sprints by treating each sprint as a chance to run a design experiment.

What is lean UX design?

Lean UX design is the application of lean startup thinking and agile working to user experience design. It prioritizes outcomes for users and the business over polished design documents.

Gothelf and Seiden wrote that the aim is to reduce waste by focusing on the experience being designed, not on deliverables. Their book draws on the lean startup method popularized by Eric Ries and on agile practice.

People also search for 'lean user experience' or 'lean UX methodology'. These phrases describe the same approach.

What are the principles of lean UX?

Lean UX rests on a few principles. These are cross-functional teams, small self-organized groups, a focus on outcomes over outputs and learning through experiments. Gothelf and Seiden describe a longer list in the book.

Cross-functional means designers, developers, product owners and others work on the problem together. Everyone shares what they learn.

Outcome focus means judging work by what changes for users, not by how many screens you produced. A finished wireframe is an output. A user completing a task more easily is an outcome.

Permission to fail is also part of the mindset. A failed test is useful information, as long as the team learns from it.

How does the think-make-check cycle work?

The think-make-check cycle is a loop in which you form a hypothesis, build a quick test of it and check the results with users. You then repeat with what you learned.

The cycle works like this:

1. Think: state the assumption and what outcome you expect.

2. Make: build the smallest artefact that can test it, such as a sketch, a clickable mock-up or a simple page.

3. Check: show it to users or measure behavior, then decide whether to continue, change or stop.

This mirrors the build, measure, learn loop of lean startup. Shorter loops mean you spend less time on ideas that do not work.

How do you write a lean UX hypothesis statement?

A lean UX hypothesis states what you believe, who it affects and how you will know it is true. A common form is: we believe that doing this for these people will achieve this outcome.

Add the evidence you will use: we will know we are right when we see a measurable change.

Here is an illustrative example. We believe that adding a progress bar to the sign-up form for new customers will reduce abandoned sign-ups. We will know we are right when more people finish the form.

A good hypothesis names a user, a change and a signal. If you cannot say what would prove it wrong, rewrite it.

What is the lean UX canvas?

The Lean UX canvas is a one-page tool created by Jeff Gothelf that frames a problem and guides a team from assumptions to experiments. It is a facilitation aid for a team session.

It moves through the business problem, the intended business outcomes, the users and their benefits, the proposed solutions, the hypotheses and the riskiest assumptions. Teams then choose experiments to test.

It plays a similar role to the Lean Canvas for startups. It is aimed at product and design teams working on a specific problem inside a larger business.

How do you run MVPs and experiments for UX?

In lean UX, you run the smallest test that can answer your question. This might be a paper sketch, a prototype, a landing page or a small live change.

The idea matches the minimum viable product concept. For a new feature, the MVP could be a manual process behind a simple screen. You then learn whether users want it before you build the real thing.

When you have enough traffic, you can compare two designs with live users. The A/B testing tools category describes software for this. For interviews and feedback, see the customer discovery tools category.

Keep experiments small and time-boxed. Say you test a new button label with a few hundred visitors over a week. The result guides the next step, not a final verdict.

How does lean UX fit with agile sprints?

Lean UX fits agile sprints by running design and discovery work alongside development rather than ahead of it. Designers and developers work together in the same cycle.

Instead of finishing all design before coding, the team designs just enough for the next sprint and tests as it builds. Findings feed into later sprints.

This is close to lean software development, which also treats learning as central. The lean agile software hub gathers related tools.

What are common lean UX mistakes?

A common mistake is treating lean UX as an excuse to skip research. Quick tests need real users, not only colleagues.

Another is testing without a clear hypothesis. Without one, you cannot tell what the result means.

A third is keeping design inside a silo. If developers and product managers only see the output, the team loses the shared learning that lean UX depends on.

Frequently asked questions