Understand the task and context
Identify who uses the product, what they need to finish and the conditions in which they work. A cashier handling a queue has different needs from a buyer comparing services on a phone. Review current support questions and workflow friction before adding interface complexity. Treat assumptions as questions to test, rather than as established customer facts.
Architecture before polish
Map navigation, content priority and the states a journey can enter. Include errors, empty results, pending work and permission restrictions in wireframes. A prototype should clarify what happens after a click, not only how the first screen looks. Define the language of controls so users can predict the result of an action.
Accessible interaction and motion
Use readable text, visible focus, adequate target sizes and meaningful labels. Do not rely on color alone to communicate status. Motion should explain a transition and respect reduced-motion preferences. Important copy and actions should remain available when an animation fails or JavaScript loads slowly. Validate long content and small screens before approving a component.
Design handoff and validation
Document component states, spacing, content rules and interaction behavior. Review the rendered implementation because browser behavior can differ from a design file. Observe representative users completing key tasks where research access is available. Record unresolved questions instead of inventing research findings. Bring current screens, brand assets and the most important user journey to a design review.