What should a UX audit include?
A good UX audit ends with a decision your team can act on, not a lengthy report that sits unread. Here’s what should be in it.
Guides
Practical guides for productteams and new businesses
Guidance on UX audits, complex B2B workflows, design leadership and launching a new business, drawn from more than ten years of product work in banking, telecoms and enterprise software.
What drives the cost of a UX audit?
The cost of a UX audit depends far more on scope than on who does it. Here’s what moves the number, and what you should get for it.
Seven signs your product needs a UX audit
Most teams don’t need an audit because their product is broken. They need one because they can’t agree what to fix first.
UX audit, user research or redesign?
The right starting point depends on what you don’t know yet. Here’s a quick way to work out whether you need an audit, research or design.
Heuristic evaluation vs UX audit: what’s the difference?
People use the terms interchangeably, but they answer different questions. One checks an interface against principles. The other helps you decide what to do next.
How to scope one product workflow
A narrow scope can still tackle a big business problem. The key is to follow one complete task, not an arbitrary set of screens.
How to prioritise UX findings without guesswork
A long list of issues isn’t a plan. Good prioritisation explains what matters, why, and what you still need to find out.
How to find friction in B2B onboarding
The best onboarding isn’t always the shortest. It gets the right person to a useful outcome, with confidence, even when they need someone else’s help.
How to prepare for a UX audit
A little preparation gives the reviewer enough context to make sharp recommendations, without turning the audit into a discovery project.
Map a workflow before you draw screens
A good workflow map shows the decisions and handovers. It doesn’t need to capture every detail to be worth having.
Make approval handovers clear
When work changes hands, people need to know what changed, who owns the next step and what they’re allowed to do.
How to design roles and permissions in B2B software
Permissions decide what each person can see and do. Get the model wrong and no amount of interface polish will fix the confusion.
Design the states everyone forgets
Most designs only show the happy path. Engineers then have to guess what happens when there’s no data, slow data or no access. Here’s how to stop that.
Design dashboards around decisions
A dashboard earns its place when it helps someone understand what’s going on and decide what to do about it. Here’s how to design one that does.
Design forms that help people recover from errors
Errors will happen. A good form is judged by how well it helps someone carry on afterwards.
Prototype the risky parts first
A prototype earns its keep when it settles a specific question before the team commits to building. Start there, not with the screens.
Design an AI assistant that helps people get things done
Most AI assistants stop at answering questions. The useful ones help people finish a task, safely, without leaving the journey they’re in.
Design self-service support that resolves problems
Self-service works when it’s designed as a set of decisions, not a library of articles. Here’s how to build support journeys that get people to an answer.
Run a design review that moves work forward
A good design review leaves the designer and the team clearer about the next decision. Consensus on taste isn’t the goal.
Fractional design lead or Head of Design: which do you need?
If you have a few designers and nobody senior guiding the work, you might not need a full-time hire yet. Here’s how to tell.
How to work well with an async design partner
You don’t need someone in your stand-up every morning to get senior design work done. You need a clear rhythm, good written context and decisions that stick.
How to choose a UX consultant: 10 questions to ask
Portfolios all look good. The right questions tell you whether someone can solve your problem, and whether you’ll work well together.
When a component library isn’t enough
Reusable components help teams work consistently. Shared decisions are what make that consistency worth having.
Make design handover easier for engineers
A design file shows what the interface should look like. A good handover helps the team understand how it should work, and why.
How to measure whether a design change helped
Shipping a design is a delivery milestone. Knowing whether it helped needs a different question, and some planning before launch.
How to write a website brief for a new business
A good website brief explains what the site needs to help a customer decide. Pages and visual references come later.
Website launch checklist for a new UK business
The things that are easy to forget when a new business site goes live, from your registered office address to the image that shows up when someone shares your link.
What brand identity does a new business need?
You don’t need a 60-page brand book to launch. You need a few well-made essentials that look consistent everywhere your customers meet you.
How to choose a website platform for your business
The right platform is the one your business can run well after launch. Start with the work the site has to do, then pick the tool.
How to get your small business found in AI search
More customers now ask an AI assistant before they search. Here’s how to help those assistants understand who you are, what you do and why you’re credible.
Make your website and profiles work together
Your website and your profiles don’t need identical copy. They need to help the same customer understand the same business.
Our guides are written by Marian Cozma with AI drafting support, reviewed before publishing and linked to their sources. Examples are illustrative unless they link to a case study.
Put the reading to work
A workflow that needs attention?
A UX Audit reviews one critical workflow and sets out what to fix first.