Interfaces that do the job.
Clear signage for software: people should know where they are, what they can do and what happens next.
Scope
What this covers
Good interface design is closer to wayfinding than decoration. We study how people actually use a product — through interviews, observation and the support tickets and analytics you already have — then fix the routes they struggle with.
Outputs range from a quick heuristic audit with prioritised fixes to a complete design system with tokens, components and usage rules. All designs are annotated for accessibility and handed over in a form developers can implement without guesswork.
Method
Sequence of work
- 01
Audit
Heuristic and accessibility review of current screens.
- 02
Research
Interviews or moderated tests with representative users.
- 03
Structure
Information architecture, user flows and wireframes.
- 04
Design
High-fidelity UI with all states: empty, loading, error, success.
- 05
System
Design tokens, component library and developer handover notes.
Spec sheet
Working parameters
| Tools | Figma, shared prototypes, moderated remote testing |
|---|---|
| Accessibility | Contrast, focus order, target size, motion, screen-reader annotation |
| Outputs | Audit reports, flows, prototypes, UI files, design system |
| Handover | Named components matching code, spacing and type tokens |
Questions
Asked on the desk
Do you design without building?
Yes. Several clients use bay B3 alone and hand the designs to their own developers.
How many users do you test with?
Usually five to eight per round, which reliably surfaces the main problems.
Can you work with our brand guidelines?
Yes, and we flag where they clash with accessibility requirements.