Instead of a full UX audit, start with a one hour review

On-Off Group

October 2026

A one hour review is a workable UX audit alternative. Take the two or three screens customers actually use, check them against usability standards, write down the problems and one number you can measure again later, then decide whether a bigger audit is worth buying.

You have a quote for a UX audit, and weeks of waiting before anything lands on your desk. Your boss wants to see something from the customer journey work this month.

There is a cheaper way to start. Take the flow that matters, review it against usability standards in about an hour, write down what is wrong and one number you can measure again later. Then decide whether you still want the audit.

Useful if you have already run customer journey sessions and know what usability testing costs.

What the audit quote is really buying you

Most audit proposals cover the whole product. Every screen, every state, a scored report against a checklist of usability rules, plus a workshop to present it. The work is usually fine. It just arrives too late and too big to act on.

By the time the report arrives you have a long list of findings, no order of importance that matches your roadmap, and releases that have moved on already. Someone still has to work out which of those findings are worth a ticket, and that someone is you.

And the report tells you what is wrong today. It does not tell you what things were like before, so when your boss asks whether the fixes worked, you are back to shrugging. Clients tell On-Off Group the same story: the review was done, the redesign shipped, and nobody can say whether turnaround time on onboarding went up or down, because the starting number was never written down.

Review one flow, not the whole product

Pick the flow that generates the most complaints or the most manual work for branch staff. Onboarding, a claim submission, a loan application. Two or three screens, not the whole app.

Get two or three people in a room for an hour. Someone from digital, someone who handles complaints, someone from ops who sees what comes out the other end. Go through the flow on a real device with a real account. Check it against ordinary usability standards: are the labels the words customers use, does an error message say what to do next, how many fields are there that the bank could fill in itself, what happens when the upload fails.

Write each problem down as one line. Then order them by how much pain they cause, not by how hard they are to fix. We have written up the method we use, screen by screen, in How to review a website or app against usability standards in 60 minutes.

Write down one number before you change anything

This is the part that gets skipped, and it is what your boss will ask about.

Before any fix goes in, pick one number from the flow you just reviewed. Completion rate. Turnaround time from submission to approval. The number of applications branch staff have to correct by hand each week. You almost certainly have it already in a report somewhere.

One number is enough. It has to be one you can pull again in six weeks without a data request that takes a month.

A large insurer we worked with ran five day design sprints on customer-facing web journeys and measured the result themselves. Journeys that used to take six months or more were designed and tested with customers in two weeks and live in four. Completion rates on the new journeys went up 80 percent against the number recorded before the work, measured by the insurer, and the old drop-off points disappeared. None of that is provable without the before number.

Fix three things, ship them, measure again

The review gives you a list. Take the top three. Not thirty.

Three small fixes are usually easy to get into a release, and if you picked the right three the number should move. Ship them, wait a few weeks, pull the same measure.

If it moved, you have evidence, and the next request for budget is easier because you are no longer asking anyone to take a redesign on faith. If it did not move, you learned that the problem is not on those screens. That is worth knowing before you spend eight weeks auditing them in detail.

The same approach works on bigger plans. Instead of a platform project, ship one customer journey, measure it, then widen. That one is written up here: Instead of a platform project: ship one customer journey, measure it, then widen.

When the full audit is still the right buy

Sometimes it is. If you are about to replatform, or a regulator has asked for accessibility evidence, or you are inheriting a product nobody on your team built, a full audit earns its money.

Buy it with a shortlist in hand and a number already recorded, so the report gets read against something. You can also tell the supplier where to concentrate, which usually makes the work shorter.

The same logic applies when someone offers to write you a strategy first. Size the gap before you buy the fix, which is the argument in Instead of hiring a strategy consultant, size the gap in two weeks.

And if you are thinking of putting AI on top of the flow, do the review first. Putting AI on a flow that already confuses customers just makes the same mistakes faster.

What to do this week

Pick one flow: the one with the most complaints or the most manual work for branch staff.
Book an hour with two or three colleagues, including someone who deals with the complaints.
Go through the flow on a real device and write each problem as one line, ordered by pain.
Pull one number off that flow today and write it down with the date.
Choose three fixes, get them into the next release, and put a date in your calendar to pull the same number again.

Questions people ask

What does a one hour UX review actually cover?
One flow, usually two or three screens, checked against standard usability heuristics: labels, error messages, form length, what happens on a failure. You end with a written list of problems in the order they hurt and one measure to compare against later.

Is a one hour review enough to replace a full UX audit?
Not always. It is enough to tell you whether a full audit is worth buying, and it gives you the baseline number the audit will need anyway.

What number should we write down before we change anything?
Something already in your reports: completion rate on the flow, turnaround time from submission to approval, or the count of applications branch staff have to fix by hand.

Who should do the review?
Two or three people from your own team, including someone who handles the complaints. An outside reviewer helps, but the main cost of an audit is the waiting, not the expertise.

On-Off Group trains teams, tests products with real customers, finds where a transformation has stalled and builds what gets it moving, for banks, insurers and enterprises in the Philippines, since 2015. How we help with ux review.