Prototype
A prototype is an interactive, testable model of a product used to validate ideas and interactions before they are fully built.
A prototype answers questions that static designs cannot — how a flow feels, whether an interaction is clear — while the cost of changing it is still low. Prototyping well shortens the distance between a sketch and a shipped product.
How it works
A prototype fakes just enough of a product to answer a specific question. Low-fidelity prototypes, clickable wireframes, test whether a flow makes sense. High-fidelity prototypes with real visuals and motion test how an interaction feels. Coded prototypes test what only real data or real devices reveal, such as performance or an unusual input method.
The question comes first; the fidelity is whatever the cheapest way to answer it turns out to be.
Example
Before building a multi-step booking form, a team can click five people through a prototype of the steps and watch where they hesitate. If most stall at choosing a time slot, the design changes there, in minutes, before any booking logic is written.
In practice
Before a prototype is built, agree the questions it should answer, such as whether customers can find the right service, complete a booking without help, or understand the price. The questions decide how detailed the prototype needs to be and who should test it. Ask your designer to keep fidelity low where the question is about structure and only add polish where the question is about feel or trust. That keeps cost down and stops discussions drifting to colours.
When you watch a test, resist explaining. Give the person a realistic task, such as booking a cleaning for next Tuesday, and stay quiet while they try. Hesitations, wrong clicks and comments like "I expected" are the findings. Write them down, group them, and fix the ones several people hit. Make clear to everyone involved that the prototype is disposable: it may look finished, but it usually has none of the security, data handling or error handling a real product needs. A developer should build the real version properly rather than extending the prototype unless it was built for that purpose.
Why it matters for your business
A prototype is the cheapest place to discover that customers find your booking flow confusing. Changing it there takes hours; changing it after the software is built can take weeks and a second invoice. It also settles disagreements inside the business, because people react to something they can click rather than arguing over descriptions. A short round of usability testing on a prototype often reveals problems nobody in the room predicted. It is not always needed: a standard contact page or a simple brochure site follows patterns that are already proven. Prototype the parts that carry money or effort for the customer, such as checkout, booking or a multi-step user flow.
Common mistakes
- Polishing a prototype until it looks finished, so stakeholders treat it as the product.
- Testing with colleagues who already know how it is supposed to work.
- Shipping prototype code to production because it "already works".
Questions people ask
What tools are used to make prototypes?
It depends on the question. Paper sketches and whiteboards work for very early flows. Design tools such as Figma let designers link screens into clickable prototypes without code. When the question depends on real data, speed or device behaviour, a quick coded prototype is better. The cheapest tool that answers the question is the right one.
How many people do I need to test a prototype with?
Fewer than most expect. A handful of people from your real audience, often around five per round, usually reveals the biggest problems, because they tend to stumble in the same places. Fix what you find and test again with a new handful, rather than running one large session.
Is a prototype the same as a mockup?
No. A mockup is a static picture of how a screen will look, with final colours, type and images, but nothing to click. A prototype is interactive, so people can move through it and you can see where they hesitate. Mockups test appearance; prototypes test behaviour and flow.