User First
Product Design (UX/UI).
Research → UX → UI → Design System
Research, interaction and interface design, ending in a component system your engineers can build from. Not a set of screens that look right in a presentation and fall apart the first time someone resizes a window.
Who this is for
You have a product that works and nobody uses it, or a product that tests well and cannot be built. Both are design problems, and they are different ones.
What you get
Artifacts, not activities.
- 01
Research synthesis
What users actually do, from interviews and session data, separated from what they say they do, which is a different document.
- 02
Interaction model
The product's nouns, verbs and states, named consistently. Every later disagreement about a screen is really a disagreement about this.
- 03
Component system
Figma library and the tokens behind it, with every state drawn: empty, loading, error, partial, too-much-data.
- 04
Accessibility contract
WCAG 2.2 AA as a build requirement with the specific criteria that apply, not a badge in the footer.
- 05
Handover kit
Redlines, motion specs and the written reasoning for the three decisions an engineer will be tempted to undo.
How it runs
Every phase has a duration on it.
Weeks 1–2
Find out
Interviews, session review, and a walk through the product with the people who support it. The support queue is the most honest research instrument in the building.
Weeks 3–5
Model it
Interaction model, flows and the first component pass. Tested against the real data, including the records that are forty characters long.
Weeks 6–8
Make it buildable
The system, the states, the accessibility contract and the handover. Reviewed by the engineers who will build it before it is called done.
What it's built on
Named, so you can hire for it later.
We publish the stack because one of our refusals is building on something you cannot staff after we leave. If a choice here does not suit your hiring market, that is a conversation for week one, not a surprise in year two.
Design
- Figma
- Design tokens
- Variable fonts
- Motion specs
Research
- Moderated interviews
- Session replay
- Task analysis
- Diary studies
Handover
- Storybook
- Token pipeline
- Redlines
- Written rationale
What good looks like
The numbers we hold ourselves to.
- 2.4×
Task completion
Median across redesigned core flows
- −61%
Support tickets
On the flows that were redesigned
- AA
WCAG 2.2
Verified, not asserted
These are the targets we work to on this kind of engagement, not averages from past ones. Measured outcomes carry a baseline, a period and the name of whoever measured them, and they live in See Impact in Action.
Ready to scope product design (ux/ui)?
It starts the same way every engagement does — four weeks, fixed scope, fixed price, and eight artifacts you keep whether or not you build with us.
The Usool Method
- Principle
- Pattern
- Prototype
- Production
- Proof