Use when
- A risky assumption needs evidence before build.
- A team needs quick feedback on a concept, journey, dashboard, or admin workflow.
Best for
- Concept validation
- Testing risky flows before development
- Comparing alternatives quickly
How to design it
- Choose the lightest prototype that can answer the question.
- State the prototype’s assumptions and limitations clearly.
- Keep the output tied to decisions, not just reactions.
Prototype Test TemplateUse this when you need a practical starting template.
View template
- What decision is this prototype meant to support?
- What assumptions are intentionally not represented?
- What would count as strong enough evidence to continue?
Output
- Concept validation notes
- Flow decisions
- Risks to investigate further