03 / UI/UX Design
UI and UX are two jobs. We do both, in the right order.
Collapsing them is how teams end up with beautiful software nobody can operate. Structure first, then flows, then the interface. Then we watch real users try it, and fix what we got wrong.

Interfaces people can use without being taught.
What we do
- Design the information architecture and user flows before anyone draws a screen.
- Wireframe, prototype and design the interface, including every state the happy path ignores.
- Run usability testing with real users and change the design based on what we watch them do.
- Audit existing interfaces against evidence, heuristics and WCAG 2.2 AA accessibility.
Problems we solve
The situations clients arrive with
If more than one of these sounds familiar, they are probably the same problem seen from different seats.

- 01
It looks good and nobody can use it
The screens photograph beautifully. In practice users hesitate, backtrack and contact support, because the structure underneath was never designed.
- 02
Every screen is a different product
Six teams, six interpretations, no shared patterns. Users relearn the interface each time they move between sections.
- 03
Nobody has watched a user use it
Decisions are settled by whoever argues best in the room. There is no evidence in the conversation, so the same debates repeat every quarter.
- 04
Accessibility is a late-stage surprise
A procurement questionnaire or a legal notice arrives and suddenly the whole interface needs auditing. It is far cheaper built in than bolted on.
Who this is for
- Teams shipping a new interface who want it tested before launch, not after
- Products where the same task is done differently on every screen
- Companies facing an accessibility requirement they cannot currently meet
- Founders who need a designer who will run the research as well as draw the screens
Capabilities
Structure
- Information architecture
- User flows
- Wireframing
- Navigation design
- Content design
Interface
- UI design
- Interaction design
- Motion design
- Responsive design
- Dark mode & theming
- Prototyping
Evidence
- Usability testing
- UX audits
- Heuristic evaluation
- Accessibility (WCAG 2.2 AA)
- Design QA
Our approach
How we work on this
Four positions we hold consistently, including the ones that occasionally make a first meeting uncomfortable.
Wireframe in words first
Before a layout exists we write what each screen has to say and in what order. Most layout arguments are unresolved content arguments wearing a visual costume.
Density is a decision, not a default
A tool used for eight hours a day should show more, not less. A consumer app opened once a week should show less. We pick deliberately rather than applying a house style.
Test with five, not fifty
Five task based sessions find most of what is broken. We run them early and often rather than saving research for a single large study nobody acts on.
Accessibility at component level
Focus order, contrast, labelling and keyboard operation are solved once in the system rather than audited feature by feature forever.
Process
Six stages, each a decision point
Every stage produces something you could act on if you stopped there. That is deliberate. It keeps the engagement honest.
- 01
Frame
Agree the tasks the interface must support, who performs them, how often, and under what conditions. This is the brief the design gets measured against.
Outputs
- Task inventory
- User & context notes
- Success criteria
- 02
Structure
Information architecture, navigation model and end to end user flows, agreed before any visual work begins.
Outputs
- Information architecture
- User flows
- Navigation model
- 03
Wireframe
Low fidelity layouts that settle hierarchy, content and sequence without the distraction of colour and type.
Outputs
- Wireframes
- Content hierarchy
- Annotated screens
- 04
Design
Full interface design across breakpoints and states, with interaction detail, motion and responsive behaviour specified rather than implied.
Outputs
- UI design
- All interface states
- Interaction & motion specs
- 05
Test
Task based usability testing on a clickable prototype, plus accessibility review. Findings get designed out before the build starts.
Outputs
- Usability findings
- Accessibility report
- Revised design
- 06
Systemise
Components, tokens and documentation so the next twenty screens are composed rather than reinvented, then design QA during the build.
Outputs
- Component library
- Design tokens
- Design QA
What changes as a result
Higher
Task completion
Measured before and after on the tasks that actually matter.
Fewer
Support contacts
The interface stops teaching people to email you.
AA
Accessibility standard
WCAG 2.2 AA built into components rather than audited per feature.
In their words
What clients say after the work ships.
FAQ
About ui/ux design engagements
UX design determines what the product does, how it is structured and what sequence of decisions a user moves through. UI design determines how that is expressed visually and interactively through hierarchy, typography, colour, density and motion. Good UI cannot rescue poor UX. Good UX with poor UI is usable and unconvincing.
Related reading
The thinking behind ui/ux design
Also in the studio
Our other capabilities
Most engagements draw on more than one practice. These are the ones that usually sit next to this one.
02AI & Product DesignWe turn complex product problems into simple, useful digital experiences.Product designSaaS designMobile app designEnterprise UX+9 moreExplore AI & Product Design
01BrandingWe build brands people understand, remember and trust.Brand strategyBrand positioningBrand identityVisual identity+8 moreExplore Branding
Clients who trust us.









