Services
UI and UX design
Research, structure and interface design that ends in something buildable, not in a folder of pictures.
Decisions grounded in evidence
Interviews with the people who will actually use the thing, a review of how the current product is used, and a written summary of what we learned.
- User interviews and usability testing
- Review of existing analytics and support tickets
- Findings tied to specific design decisions
Structure first
What lives where, what is named what, and what a person is trying to do on each screen. Most interface problems are structure problems wearing a visual costume.
Designed for the real state
Empty, loading, error and too much data, not just the demo screen where everything is perfect. The unhappy paths are where products lose people.
Components, not screenshots
Tokens, components and usage rules documented so the tenth screen costs less than the first and a new engineer can build one without guessing.
Built the way it was drawn
We stay involved through the build and review the implementation, because a design that is never built correctly was never really finished.
What we build with
Accessibility is part of design here, not a remediation phase. Contrast, focus order and target size are decided at the same time as the layout.
How the work runs
Learn the users
Interviews, a review of the current experience, and a written statement of who we are designing for and what they are trying to do.
Structure then surface
Flows and wireframes agreed before visual design, so debates about colour do not stand in for debates about structure.
Prototype and test
A clickable prototype put in front of real users, then revised. Changing a prototype is cheap and changing production is not.
Support the build
Component documentation, design review during implementation, and updates to the system as the product grows.
Questions we get asked
Do you design without building?
Yes. Design engagements stand alone, and the output is documented components and flows that any competent engineering team can build from.
Can you work with our existing brand?
Yes. We work inside an existing brand where one exists, and extend it into an interface system where the brand stops at a logo and a colour.
What do we receive at the end?
A Figma file organised for engineers rather than for a presentation, documented components and tokens, the prototype, and a written summary of the research behind the decisions.
Do you run user testing?
Yes, usually with five to eight participants per round. Small rounds run often find more than one large round run late.
How do you handle accessibility?
We target WCAG 2.2 level AA from the first wireframe. Contrast, focus order, target size and screen reader labelling are design decisions, not a fix applied at the end.
Product not landing with users?
Show us the product and tell us where people fall away. We will propose a design engagement scoped to that problem.