Services · Design
Design that answers a question, not just decorates one
The cheapest place to find out that an idea does not work is a prototype. We design to reduce what you are uncertain about — and if a screen is not doing that, it does not need to exist yet.
Talk about a productHow design goes
Four stages, front-loaded on the unknowns
The order matters. Most design work that disappoints was beautiful and answered a question nobody had asked.
We write down the assumptions the product rests on and rank them by what it would cost to be wrong. That list drives everything after it, and it is short enough to disagree with.
Interviews with the people who will use it, a look at what they do today, and a review of the system they are escaping. Sometimes that is a fortnight of fieldwork, sometimes it is four conversations — the assumption list decides which.
Something a real user can attempt a real task in. We test it with people outside the project, and we report what went wrong as carefully as what went right, because the failures are the return on the exercise.
Components, tokens, states, and the rules for combining them, documented so a developer does not have to guess and a future designer does not have to start again. Delivered as a working library, not a slide deck.
Surfaces
Where we design
Web applications
Dense, information-heavy interfaces where the users are experts and speed of operation beats first-run delight.
Mobile
iOS and Android, native or cross-platform, designed around what someone can actually do one-handed on a bus.
Wearables
Glanceable interfaces where the budget is two seconds and one piece of information.
AR and VR
Spatial interfaces for training, visualisation and field work — built where the three-dimensional version genuinely beats a screen.
Design systems
A component library with real tokens, real states and real documentation, so consistency survives the next three teams.
Accessibility work
Audits and remediation against WCAG 2.2 AA, including the manual testing that automated tools cannot do.
What you get
Deliverables that outlive the engagement
The research, written down
What we heard, from whom, and what we concluded — including the findings that contradicted the brief. You keep the raw notes, not just the summary.
A prototype you can put in front of people
Interactive and testable, in a tool you can open without us. Along with the test results and what we would change next.
A component library, not a picture of one
Named, tokenised and documented, built so the engineering team implements it rather than interprets it.
Accessibility built in from the first frame
Contrast, focus order, target sizes and reduced-motion behaviour designed in — not a remediation phase costed separately later.
Bring us the thing you are not sure about
Design is most useful before the decision is made, which is usually earlier than people call us.