Behaviour Measured
Where users stop, by task, cohort and device.
An expert review produces a list of things a reviewer would have done differently, which is a preference document. A UX audit should produce evidence: where users actually fail, how often, what it costs, and which two or three failures are worth fixing before the rest.
A finding without a measurement cannot survive an internal argument, and most of them do not.
Where users stop, by task, cohort and device.
Because aggregate data locates a problem without explaining it.
Not by section, and not thirty findings of equal weight.
Manually, not only by automated check.
What to change and what to expect, not a list of principles.
Four sources, and the strongest evidence comes from combining them.
Request an Audit →What people do, where they stop, which paths they never take.
Real attempts at real tasks, watched.
What people cannot work out, already categorised.
Useful for mechanical issues and weakest on comprehension.
Evidence gathered, findings ranked, changes specified.
For a website rather than a product, see website design audit.
Gather evidence from several sources, then rank by what each failure costs.
What the product is for, expressed as things people do.
How often each task succeeds.
Watching what happens when it does not.
Frequency times consequence, not by severity label.
Concrete enough to be implemented.
A reviewer who understands the product cannot experience it as someone who does not.
Comprehension. Once you know what a label means, you cannot un-know it, and every ambiguity that confuses real users reads as clear.
Expert review is genuinely useful for mechanical problems — inconsistent patterns, accessibility failures, states that were never designed. Those do not require a naive reader.
For anything involving understanding, five observed sessions produce more than any amount of review, because confusion has to be witnessed rather than predicted.
By frequency multiplied by consequence, not by how serious the problem sounds. A minor irritation on the most-used screen usually costs more than a severe failure in a feature few people reach.
Severity labels attached by the reviewer are a proxy for this and a poor one, because they reflect how bad something looks rather than how much it happens.
Ranking properly usually shortens the report considerably, which is the point — a client can act on three ranked findings and cannot act on thirty unranked ones.







A UX audit examines an existing product to find where users fail — through usage data, observed sessions, support volume and expert review — and ranks the findings by what each failure costs.
An expert review is one person's opinion. An audit combines that with measurement and observation, because a reviewer who understands the product cannot experience it as someone who does not.
By frequency times consequence. A small irritation on the most-used screen usually costs more than a severe problem in a feature few people reach, which severity labels do not capture.
Fewer than most audits produce. Three ranked findings can be acted on; thirty unranked ones cannot, and length is a poor proxy for usefulness.
For a marketing site rather than a product, see website design audit. The methods overlap; the tasks being measured do not.
Still deciding if ux audit is right for you?
Talk to UsExpert review is fast, cheap and requires no participants, which is why most UX audits are built on it. A skilled reviewer walks the product and lists what is wrong.
They walk it knowing what every label means, what each screen is for, and where things live — knowledge they acquired in the first hour and cannot set aside afterwards.
Every ambiguity that stops real users reads to them as perfectly clear. It is the one category of problem the method cannot detect, and it is usually the category doing the most damage.
Give us access to your product and its usage data. We will measure where tasks fail and rank what is worth fixing.
