Problem
01
Users cannot find or finish key tasks.
02
Every screen looks and behaves differently.
03
Accessibility is an afterthought.
Outcomes
- Interfaces people can actually use
- Consistent quality as you scale
- Accessibility you can evidence
Scope
In scope
- Interaction and visual design
- Design system
- Prototyping
Not included
- User research, which sits under user research and service design
- Engineering, which sits under custom software engineering
Approach
Discovery
We agree the users, the problem and the constraints, and how success will be judged.
Delivery planning
We shape the approach, sequence the work and set out costs, risks and a definition of done.
Build and test
We build in the open, test with real users and real data, and prove it before release.
Operational readiness, hypercare and closure
We hand over, support the first weeks of use, and confirm the outcome before we close.
Deliverables
UI designsDesign systemPrototypes
Technologies
Design and prototyping toolsDesign systems and component librariesAccessibility testing to WCAG 2.2 AA.
Controls
Designs meet WCAG 2.2 AA and do not rely on colour alone. Designs are tested with a range of users, including people with access needs. A design system keeps patterns consistent as the product grows. Content and labels are written in plain language.
Frequently Asked Questions
Do you follow accessibility standards?
Yes. We design to WCAG 2.2 AA and build accessibility in rather than bolting it on.
Will this scale beyond the first screens?
Yes, through a design system that keeps quality consistent as the product grows.
Ready to scope this?
Tell us where users get stuck and we will design the way through.