User journeys and task discovery
Observe what people try to do and why current interactions slow them down. Record the information each task needs, the decisions involved and how people recover from a mistake. Choose the tasks to prototype first.
Information architecture and navigation
Arrange content around what users are looking for and test terms with representative people. For a dashboard, group routine work and reporting separately. For a website, keep service discovery and next steps easy to find.
Wireframes and functional prototypes
Model familiar and difficult interactions with representative content. Test alternative flows early enough to change them. Make loading, errors, permission differences and empty states visible in the designs.
Design systems and responsive behaviour
Set out reusable components, interaction states, spacing and responsive rules. Check a dense data entry page as well as sparse content pages. Document which component variations are intentional.
Usability and accessibility checks
Give participants tasks to complete and observe what they do without prompting. Check focus order, labels, contrast and recovery at a useful prototype stage. Note which issues need verification again in the build.
Developer handoff and design review
Include behaviour and content requirements alongside layout files. Review initial implementation using real text and data. Make a handoff note for exceptions that cannot be understood from a static screen alone.