Testing a Prototype Before Development
A prototype can reveal problems in the journey before the full system is built. It does not need to simulate every technical detail to test whether the structure and wording make sense.

Give people a realistic task
Choose a task with a clear outcome and let the participant attempt it without coaching. Watch where they hesitate or choose an unexpected route. Separate issues caused by the prototype's limited functionality from misunderstandings in the design itself.
Practical checklist
- Use realistic labels and sample content.
- Avoid explaining the intended route first.
- Record hesitation and wrong turns.
- Prioritise repeated misunderstandings.
How to review the result
Revise the journey when the same issue appears across attempts. A prototype review should influence decisions, not simply collect approval for a design that is already fixed.