01 / CONTEXT
Begin with an ordinary task.
Consider someone looking for a document on a shared website. Their goal is to find the right version, not to explore the navigation. Clear titles, a useful grouping, and an understandable date can matter more than a striking animation. The starting question is what the person needs to recognize.
An interface can make an action visible without making its meaning obvious. A label such as “Continue” needs enough surrounding context to explain what will follow. An unfamiliar icon may need a text label. These are small decisions with a direct effect on understanding.
02 / RELATIONSHIPS
Separate location, action, and feedback.
Navigation explains where a person is and where they can go. Controls let them act. Feedback describes what happened. When those functions look identical, a visitor may struggle to distinguish a page link from a setting or a completed action.
For example, selecting a section in a directory should identify the current section. A button that changes a display preference should indicate its selected state. A link that opens an email application should say so in its context. Consistent behavior makes the interface easier to learn.
03 / REVIEW
Leave room for different ways of using it.
People may navigate with a keyboard, enlarge text, reduce motion, or read on a narrow screen. A design should retain its structure under those conditions. Focus indicators, readable contrast, descriptive links, and meaningful headings are practical parts of that structure.
A useful review follows one task from entry to result, rather than judging isolated screenshots. Check what the person sees, what they can operate, and how they recover if they choose the wrong path. A polished appearance supports this work; it cannot replace it.