Time with real users and the people who support them, so the design starts from the job rather than a moodboard.
← Back to servicesSERVICE / 04
Interfaces that survive contact with real users.
Design that only works in the demo is decoration. We design for the long name, the empty state, the slow connection and the person using it for the two-hundredth time this month.
01 / The brief
The happy path is the easy part.
Most interfaces are designed with three tidy rows of sample data. Real ones have none, or four hundred, or a customer whose name breaks the column. That is where a design either holds or quietly starts costing support hours.
02 / What's included
What's included
Clickable work you can put in front of someone before a line of production code exists.
Components and rules developers can build from, so the tenth screen still looks like it belongs.
Contrast, focus order, keyboard paths and screen-reader labels checked as part of done, not after a complaint.
This is the part most studios skip. Once real people are using it we instrument the journeys, map the path they actually take, and change the design where reality disagrees with the plan — because the first version is a hypothesis, and shipping it is when you finally get to test it.
03 / How it goes
How it goes
- 01Understand the job
What the person is actually trying to finish, how often, and what they do immediately before and after.
- 02Structure before surface
Hierarchy, flow and naming settled while they are still cheap to change.
- 03Design the edges
The long name, the empty list, the failed payment. If those work, the happy path is trivial.
- 04Build the system
Ship it as components and tokens so it stays consistent after we hand it over.
04 / How we build
How we build
Scale, spacing and line length decided once and applied everywhere, so pages feel related without being identical.
Animation should explain a change of state. If it only decorates, it costs attention for nothing.
Rendered geometry checked in a real browser, because a design that only holds in the design file is not finished.
05 / Seen in practice
Casaweb
Casaweb turns a fragmented property search into one considered journey — search, listing detail, neighbourhood context and the tools around the decision, all in one product language.