Make the journey clear. Make the interface consistent.

An interface can look consistent while leaving a person unsure what to do. We begin with the task, the information needed at each point and the consequence of an action. This gives the review a practical purpose beyond choosing a preferred visual style.

A project may improve an existing flow, design a new product experience or establish reusable interface patterns. The scope identifies which users, platforms and journeys are included, what evidence is available and how the design will be assessed. Existing research and support feedback can inform the work; gaps remain visible as assumptions or further discovery needs.

Design-only and design-plus-build are different commissions. A prototype can explain sequence and behaviour without being production software. The proposal should distinguish research activities, design files, component guidance, planned user review and implementation work so your team knows what it is receiving.

Choose representative tasks and explain what a reviewer should be able to understand or complete. If access to intended users is included, agree recruitment, review method and responsibilities in the scope. Stakeholder feedback is useful, but it should not be presented as a completed user study.

Include the difficult state as well as the preferred path. A form can be incomplete, a result set empty or an action unavailable to the current role. The design should explain what happened and what the person can do next. Implementation constraints and unresolved business rules belong in the handover, rather than being concealed by a smooth prototype.

Imagine a catalogue interface with several filters. A person removes one choice but cannot tell which filters remain active; the results disappear without an explanation. A prototype could show the active choices, the meaning of the result count and a clear way to adjust or reset the search. The task reveals information and state-design questions, not merely a preferred card style. This is an illustrative design exercise, not an Auckland client, observed usability finding or completed product.