Home › The Garage › Prototyping
Design thinking

Prototyping & experimentation

A prototype is not a small version of the final thing — it is a question made tangible. Build the roughest thing that tests your riskiest assumption, put it in front of real people, and let the result decide.

By LeanBean · Updated November 2026 · 5 min read
What's in this guide
  1. What a prototype is for
  2. Low fidelity first
  3. Testing the riskiest assumption
  4. The build-measure-learn loop
  5. Common questions
Build (rough) Measure (test) Learn Each loop is cheap and fast — the point is to learn, then decide to persevere or change.
Build the least you need to answer the question, test it, learn, and go round again.

What a prototype is for

A prototype exists to answer a question you can’t answer by arguing — will people understand this? will they use it? does this step work? It is a learning tool, not a deliverable. The sooner you have something concrete in front of real users, the sooner reality replaces opinion, and the cheaper it is to be wrong.

Low fidelity first

Match the roughness to the question. Early on, a sketch, a paper mock-up or a walk-through is enough — low fidelity, built in minutes, easy to throw away. Polishing too early wastes effort and, worse, makes you reluctant to change a thing you’ve grown attached to. Raise fidelity only as the questions get more specific and the risky assumptions have been retired.

Testing the riskiest assumption

Every idea rests on assumptions; one or two of them, if wrong, sink the whole thing. Find that riskiest assumption and design the prototype to test it first — not the easy, comfortable parts. If the idea is going to fail, you want it to fail now, cheaply, while there is still time and budget to change course.

The build-measure-learn loop

The output is a decision, not a prototype
Each cycle — build the least you need, measure it with real people, learn from what happens — ends in a choice: persevere, change the approach, or stop. A prototype that teaches you to abandon a bad idea has done its job perfectly. This is the same discipline that turns a transformation idea into a tested step rather than an expensive bet.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

The Garage — a community of practice

The Garage is where Lean, process and AI-readiness practitioners learn in the open — short lessons, real examples, and a place to compare notes. Join the community: follow along, try it on your own work, and share what you find.

Common questions

What is the purpose of a prototype?

To answer a question about an idea by making it tangible and testing it with real people, before committing time and money to building the full thing. A prototype is a learning tool, not an early version of the product.

What is low-fidelity prototyping?

Testing an idea with the roughest possible artefact — a sketch, paper mock-up or walk-through — built quickly and easy to discard. It answers early questions cheaply and avoids the attachment that comes with polished work.

What is a riskiest-assumption test?

Identifying the assumption that would sink the idea if it were wrong, and designing the prototype to test that first. It surfaces fatal flaws early, while changing course is still cheap.

What is the build-measure-learn loop?

A fast cycle of building the least you need, measuring how real users respond, and learning enough to decide whether to persevere, change the idea, or stop. The output of each loop is a decision, not just a prototype.

Related guides: Human-centred design · Brainstorming & ideation · Transformation roadmap