Prototype explained
A prototype is a model for trying flows or interactions before building a complete product. It can be as simple as paper or look close to the final product. The level of detail follows the question being tested: paper can probe a flow, while a detailed model can probe interaction and content expectations. Realistic data and edge cases make the exercise more informative.
Why it matters.
Trying a working flow reveals problems that static screens may hide. Changes are easier to make before development begins. Prototypes provide early feedback but may not reproduce a working product's speed, accessibility, or technical limits. Findings should note which parts of the model were unrealistic.
Let's look at an example.
Think of a ticket purchase idea.
A team connects screens into a clickable prototype. If people look for pricing while choosing seats, the team can address that before building the product. If the total changes during seat selection, the prototype should show that change. Otherwise a person's search for the price may flag a real need while leaving the test incomplete.
How to apply it.
- 01
Choose the question you want to test.
- 02
Create only the screens and interactions needed.
- 03
Observe both what people say and what they do.
“A prototype represents a question to learn from, not a finished product.