User research
Interviews, analysis of what exists, a record of what actually blocks people. Not a sticky-note workshop among ourselves.
Services UI / UX design
Research, journeys and interface design
Research, journeys, clickable mockups tested with real people, then a design system your teams can take over without us.
The steps that move the product forward
Understand
Interviews, analysis of what exists, measurement of the current journey where there is one.
Structure
Journeys and zoning, approved in greyscale before any visual decision.
Draw
Complete mockups, states included: empty, loading, in error.
Test, then deliver
Test sessions, fixes, then delivery of the design system and its documentation.
What we put in place
Journeys and structure
The path of every task, screen by screen, before any drawing tool is opened.
Clickable mockups
Usable on the right device, not images placed side by side.
User testing
Real people, real tasks, and a report of what failed.
Design system
Colours, type, components and states, documented in Figma. One more screen is then drawn without us.
Handover to developers
Measurements, behaviours, edge cases. What a mockup leaves out is exactly what gets decided badly at the end.
When this area makes the difference
- Existing products whose users drop out along the way.
- Teams that develop without mockups and build the same screen twice.
- Projects that have to be shown, to a board or an investor, before being built.
The questions worth asking before starting
Yes. The design system is delivered in Figma with its documentation, and your developers take it from there. It is in fact the best way to check that it is clear.
Five are enough to surface most of the blockers on a given journey. Beyond that, the same problems come back.
We change it. That is exactly what the test is for, and it is far cheaper at that point than after development.
Also worth a look
Does this format answer your challenge?
Give us a few pointers about your business and your priorities.
Take stock