UX audit
A team can see the problem in the numbers but not in the interface. An audit finds where it breaks, and why.
01
The question
A team arrives with a symptom — a drop-off, a support queue, a feature nobody uses. The brief is usually a number. The job is to turn it into a question about behaviour.
02
Investigation
Who is actually in this flow, what they are trying to finish, how much time they have, and what they are feeling at the moment they leave. Written down before a single screen is judged.
03
The problem, named
Each break located on the screen it happens on, with the impact it has spelled out. Not a list of preferences — a list of causes, ordered.
04
A proposal
Redesigned screens that answer the named problems, and the measures that would show it worked.
What you get
- A written audit — every finding on the screen it occurs on, with its impact
- The problems named and ordered by what they cost
- The flow mapped end to end, with the task the user must complete at each step
- A redesigned flow for the steps that break
- Success measures, split into primary and secondary
- A walkthrough session with whoever has to act on it
Who it suits
- A funnel that leaks at a step nobody can explain
- A product that tests well in demos and badly in use
- An interface that has grown feature by feature and stopped adding up
- A team that suspects the problem is pricing, or onboarding, and wants to know which