User research
Short interviews with five or six real users, before anything is drawn. That is usually enough to kill the wrong idea while it is still cheap.
UI and UX design
from real data.
Design is the cheapest stage at which to find out that an idea does not work. A flow can be changed in a day, while a shipped feature takes a sprint. We test the risky path with real users before any code is written.
- Research Real users, not assumptions
- Structure Flows before pixels
- System Tokens your engineers build from
- Access Keyboard and contrast as a floor
What we do
The pieces of work we do. Take all of them, or start with the ones that unblock the build.
Flows and information structure
Most product problems are structural: steps in the wrong order, too many choices at once, a state nobody designed.
Wireframes, then final screens
We map the flow, review it, then draw. You review clickable work rather than a mood board, and the final screens come last on purpose.
A design system
Tokens, components and the rules for using them. The tenth screen looks like the first one, even when a new engineer builds it.
How the screens get builtUsability testing
On the risky path only. We test the thing that would cost a sprint to get wrong, not the thing that is easy to test.
QA and testingHow the work runs
The same order every time, and nothing is drawn before the structure is agreed.
See the full service map-
Listen
We talk to five or six real users before we draw anything. What we learned gets written in plain words and shared with your whole team, not just the designers.
-
Map
The flow goes on the wall before a pixel moves. A wrong order of steps and a missing state are far cheaper to find here than in a sprint.
-
Draw
Wireframes first, then final screens against the flows we agreed. Contrast is checked as we go, not audited at the end.
-
Hand over
Tokens, components and the rules for using them. Our designers sit ahead of the engineers, in the same team, so questions get answered as they come up.
What lands in your workspace
The floor every engagement ships with. None of it is an upgrade you buy separately.
- Contrast checked on every screen, not audited at the end.
- Every control reachable by keyboard.
- Forms with real labels and real error text.
- Colours, spacing and type named as tokens.
- Components with written rules for using them.
- Designers ahead of the engineers, in the same team.
Before you ask
Answers as we would give them on a call.
Can you design without building?
Yes. Many clients bring their own engineers. We write the specs for them and stay on call through the build, so a question does not cost a week.
What if we already have a product?
Then we start with the screens that lose users. A usability pass on the risky path costs days and usually pays for the whole engagement.
How many users do you test with?
A small handful is usually enough to kill a wrong idea. Past that you are mostly paying to confirm what you already know.
Who owns the files?
You do. Tokens, components and the source files are yours from the first handover, not at the end of the engagement.
Show us the screen that is not working
One screenshot and one sentence is enough to start. We will tell you what we would change first, and what it costs to build.