Help people know what to do next.
Good design starts with what the user is trying to do and where they get stuck. We work out the flows first, test the awkward parts with a prototype, then design the screens.
Structure before polish.
Everyone arrives on a screen carrying some knowledge and a goal. A buyer opening a booking page knows the date they want but may not know which package fits. A new staff member in an admin panel knows the customer's name but not your internal codes. Design starts with that gap between what people know and what the screen asks of them.
So we map flows and rough layouts before anyone polishes a pixel. You can review the structure, move steps around and cut screens while a change costs an afternoon. Once the flow holds up, we design the interface properly. If the product itself is still taking shape, planning your first product is a useful companion read.
How a design engagement runs.
Gather what already exists
Support messages, screenshots, user complaints, analytics, the side spreadsheet your staff keep. Existing material shows where people struggle faster than a blank workshop does.
Map the flows
The main path plus its branches: missing information, a change of mind halfway, a second person who must approve. Each becomes a box on the map before it becomes a screen.
Prototype the risky parts
We build clickable versions of the interactions most likely to confuse people and try them with you, and with real users where that is possible.
Design and prepare for build
Final screens and a small set of reusable patterns for buttons, forms, tables and messages, so the product stays consistent as it grows and developers have what they need.
Design the bad moments too.
The happy path is the easy part. These states get designed alongside it.
The empty screen
A new account with no data yet. Instead of a blank table, the screen explains what will appear here and offers the first action.
The declined card
The user needs to know the payment failed, that nothing was charged twice, and what to try next, without having to phone you.
The missing document
An application can't proceed without a file. The design names exactly what is missing, lets the user upload it later, and shows your team the case is waiting.
When a person must step in
Some situations need a human. The screen says so plainly and tells the user how and when they will hear back.
What you receive.
- Flow maps for every part of the product in scope
- Clickable prototypes of the riskiest interactions
- Final screens with empty, error and loading states
- A small pattern library for consistent building
- Notes on behaviour a static picture can't show
- Design files kept in an account you own
Can you redesign just one part of our product?
Yes. Onboarding, checkout, a booking flow or one internal screen are all reasonable pieces of work on their own. We would rather understand one awkward workflow properly than redesign every screen at once.
Will the designs be ready for our developers?
Yes. We prepare every screen and state the agreed scope needs, with notes on behaviour. If our team also builds it, design and engineering stay in one conversation; see web application development.
Do you design customer portals?
Often. Portals are where design matters most, because customers visit them rarely and need to find things without help. More on that under customer portals.
How long does a design engagement take?
It depends on how many flows are in scope and how much is still undecided about the product. We agree the scope and review points first, so you see maps, prototypes and screens at set moments rather than one big reveal at the end.
Which screen do your users get stuck on?
Send us a screenshot or a description and we will suggest where a design engagement should start.