Make the task understandable. Give the interface a coherent system.

A public website, a staff application and a customer service product need different information and interactions. We establish who uses the interface, what they need to accomplish and where uncertainty interrupts the task. Available support questions, product observations and research can help define the problem, with their source and limits kept visible.

The design work can cover information architecture, task flows, wireframes, interactive prototypes, responsive visual layouts and a reusable component system. We consider meaningful content and difficult states alongside the ordinary route. A screen list is useful only when the team can explain what those screens help someone understand or do.

Design-only and design-plus-build are distinct scopes. The proposal names the design artifacts, review activities, implementation responsibilities and acceptance boundary. A prototype can illustrate a journey without executing permissions, saving production records or demonstrating the final product’s behaviour.

Access to representative users, suitable tasks and an agreed review method determines what a design evaluation can establish. We can scope those activities with your team. An internal walkthrough or expert review can be useful, but neither should be relabelled as a completed user study. Keep findings attached to the task and version examined.

Bring the development team into decisions about real data, component constraints and error responses. Include keyboard use, readable content and other relevant access needs in the brief, with a defined implementation-review scope. A design file cannot certify the built product or resolve business rules that no owner has approved.

Imagine an operator changing a single customer-facing record. The screen shows the new wording immediately, but its saved value, current draft and cancel action are indistinguishable. The person leaves and later cannot explain what was retained. A prototype could make the editing state, scope of Save and deliberate discard choice understandable, including a failed save with entered text still visible according to the approved rule. The underlying storage and permissions require implementation. This is a hypothetical interface exercise, not a New York client, observed study result or completed editing system.

For an editing journey, agree the visible meaning of unchanged, edited, saving, saved and unsuccessful states where those states exist. Other products will need their own vocabulary. Consistent styling helps only when labels and actions describe the actual product rules. Do not rely on colour alone to communicate a consequential difference.

The handover can identify the response information engineering needs to supply and the checks to repeat in the implementation. If the business has not decided whether leaving an edit discards it, keep that decision open instead of embedding a silent assumption in the prototype.