03: Design

Interfaces nobody has to think about.

Good interface design is invisible. People get what they came for and leave with no particular memory of how. Bad design is the thing they tell their colleagues about.

The short version

Most usability problems are not aesthetic. They are structural: too many choices on one screen, an unclear next step, a form asking for things nobody has to hand, an error message that explains nothing. No amount of visual polish fixes any of that.

We work from structure outwards. Who is using this, what are they trying to finish, and what is currently in their way: answered with research and testing rather than opinion, then designed into something that looks as considered as it behaves.

  • Evidence over opinion

    Decisions argued from user research and session data, not whoever is most senior in the room.

  • Tested before built

    Clickable prototypes put in front of real users while changes are still cheap.

  • Accessible by default

    WCAG AA contrast, keyboard navigation and screen reader support designed in from the start.

What's included

Everything in the box.

Scoped in writing before we start, so you know exactly what you are buying and what would be extra.

  • 01

    User research

    Interviews, session recordings and analytics review to find where people actually struggle.

  • 02

    Information architecture

    Structure, navigation and labelling, so people find things where they expect them to be.

  • 03

    Wireframes & flows

    Screen-by-screen journeys agreed before any visual design work begins.

  • 04

    Interface design

    High-fidelity screens covering the awkward states too: empty, loading, error, overflowing.

  • 05

    Prototyping & testing

    Clickable prototypes tested with real users, with findings written up plainly.

  • 06

    Design systems

    Reusable components and tokens, documented so developers build consistently without asking.

How we run it

Four stages, no mystery.

You will always know which stage we are at, what is happening next, and what we need from you to keep it moving.

  1. 01

    Research

    Understand the users, the task and the current friction, with evidence rather than assumption.

  2. 02

    Structure

    Flows, architecture and wireframes. The decisions that matter most, made before visuals distract.

  3. 03

    Design

    Full interface design on top of an agreed structure, covering every state a screen can be in.

  4. 04

    Validate

    Prototype testing with real users, then refinement and a clean handover to development.

Questions

Things people ask us.

UX is whether someone can finish what they came to do: structure, flow, clarity. UI is the visible layer they do it through: the layout, type, colour and components. They are separate skills but neither survives without the other.

Yes. We usually start with a UX audit: analytics, session recordings and a heuristic review to identify where people drop off. That often surfaces a handful of high-impact fixes worth doing before any full redesign is even considered.

Yes, and it is consistently the best value part of the process. Five sessions with people who match your audience will expose more real problems than a month of internal debate.

Routinely. You get annotated Figma files, a documented component library and a walkthrough session with your dev team, plus availability for questions while they build.

WCAG 2.2 AA is our baseline, not an extra line on the quote. Colour contrast, keyboard navigation, focus states, sensible semantics. If you need a formal audit against a specific standard, we will scope that separately.

Start here

People dropping off where they shouldn't?

Tell us what you are trying to do and we will tell you, straight, whether we are the right studio for it. No pitch deck, no pressure.

United States · We usually reply within one working day