W3 / UI/UX
Design work with dates on it.
Good design needs time to listen and test. We schedule that time explicitly, so it is protected rather than squeezed.
- Week 1: Research. Five to eight short interviews with real or prospective users, plus a review of any existing data, support messages or analytics you already hold.
- Week 1–2: Journeys. A map of the main journeys, where people start, where they hesitate, and where they give up.
- Week 2: Prototype. A clickable prototype of the riskiest journey, at enough fidelity to test honestly.
- Week 2–3: Test. Sessions with five or so people. Findings are ranked and the top issues fixed before build starts.
- Ongoing: Components. A small component library with every state designed: default, focus, hover, disabled, loading, error and empty.
Accessibility as a tracked requirement
WCAG 2.2 AA is written into the scope at Gate A. Issues are logged and tracked like any other defect, and the accessibility statement we hand over lists anything outstanding honestly.
Design decisions in the log
Why the navigation is where it is, why a step was removed, why the colour contrast changed: each lands in the decision log with a date. When someone asks “why is it like this?” a year later, there is an answer.
Deliverables
- Research summary with quotes and patterns
- Journey maps for the primary user types
- Tested prototype and the test notes
- Component sheet with all states
- Design hand-off notes for developers