Needs and current situation
We define critical tasks, user groups and important success, empty and error states. Prioritise the flows that carry the greatest uncertainty.
Possible scope
Delivery can include screen structure, interaction flows and a clickable prototype. Use representative, anonymised example data.
Prepare for the start
Prepare user scenarios, brand assets and required information. Identify reviewers who understand actual user tasks.
Checks and handover
Walk through the prototype and record confusion or dead ends. Update the flow and distinguish tested observations from assumptions.
What needs agreement
A prototype does not validate a working backend, security or production performance. Real implementation and testing remain separate.
A common question
Can a prototype be used as the finished app?
No. It demonstrates intended interactions. Its screens and findings can guide development, but require a real technical implementation.
