Design useful interactions. Give people a clear way through.

Start with the current interface or product brief and the task someone finds difficult. We review the audience, information, navigation and constraints before deciding whether the useful next step is an assessment, a focused flow or a wider redesign. Existing research, support feedback and implementation knowledge are useful inputs. New research or evaluation with participants is defined in the agreement; a design proposal should not imply that a user study has already taken place.

The work can include information architecture, task flows, wireframes, interactive prototypes, responsive visual design and reusable patterns. Use real headings, labels and representative records to explore how a person understands the next step. A consistent appearance matters, but it does not settle the meaning of a control or the result of an action.

We distinguish design files and prototype behaviour from production implementation. The handover identifies the responses the interface expects, decisions still needed from the product owner and the review to perform after development. Backend persistence, permissions and the final accessibility evaluation belong to the implemented task and agreed acceptance scope.

For the hypothetical photo flow, choose a small sequence containing two similar images. Ask the reviewer to put the named item after another using the non-drag route, then inspect the proposed order. Try a move to the first and last positions and a decision to leave without applying. The product owner must approve what each outcome means before it becomes a design convention.

Review comprehension and operation with the agreed participants and input methods. A smooth prototype is useful evidence about the proposed interaction; it is not proof of stored order, production keyboard behaviour or universal accessibility. Carry the same cases into implementation review where that work is commissioned.