Choosing the right approach
CX audit, UX audit or user testing?
They answer different questions. A CX audit looks across the customer journey. A UX audit reviews the experience of a product or interface. User testing observes people trying to complete tasks. They can work together; one does not make the others unnecessary.
The difference at a glance
| Approach | Main question | Typical evidence | Useful when… |
|---|---|---|---|
| Customer experience audit | What happens across the customer’s whole mission, and what should we fix first? | Journey evidence, purchases, service interactions, relevant research and comparisons. | Problems cross teams or you need a shared set of priorities. |
| UX audit | Where does a product or interface make things unnecessarily difficult? | Expert review of usability, content, navigation and interaction patterns. | You need a focused assessment of an existing website, app or product. |
| User testing | Can people complete these tasks, and what do they experience along the way? | Observed behaviour and feedback from recruited participants. | You need to understand customer behaviour or test a design assumption. |
When does a CX audit make sense?
Consider a CX audit when the website is only one part of the problem. A customer might find the right product easily but encounter unclear delivery promises, a confusing first-use experience or a difficult refund.
For example, “buy the right coffee machine and make a decent first cup” could involve product advice, checkout, delivery, packaging and instructions. Reviewing the checkout alone would answer a narrower question.
CX.TESTED adds an external comparison: we repeat the same missions with at least two competitors or best-in-class alternatives. The result is evidence and a short list of what to tackle first. See the audit scope and price.
When is a UX audit the better starting point?
A UX audit can be a good fit when the question is concentrated in a website, app or particular flow. You might need to review navigation, product information or the steps in a checkout before a redesign.
“UX audit” is not a single fixed package. Some include analytics, accessibility checks or customer research; others are an expert review. Ask what is included and what evidence will support the recommendations.
A broader CX audit is not automatically better. If you know the decision is limited to one interface, a focused review may give you the answer you need.
When should we use user testing?
Use user testing when you need to see how people actually tackle a task: what they notice, misunderstand, expect or fail to find. It can be used with an existing service or a prototype.
Expert review can identify likely problems. Observing customers can confirm, challenge or uncover things an expert did not anticipate. Neither should be presented as the same kind of evidence.
CX.TESTED uses customer input and existing research where useful, but a three-mission audit is not the same as a dedicated participant-based usability study. If that is what your decision needs, keep it in the plan.
Further reading: Nielsen Norman Group’s explanation of usability testing.
Can we use more than one?
Yes. An audit can identify where further investigation is worthwhile. User testing can explore a specific issue in depth. A design review can assess proposed changes, and experiments can help measure their effect.
A sensible sequence depends on the question and the evidence you already have. We would rather help you choose the right work than suggest an audit answers everything.
Are you deciding what to prioritise across the journey, how to improve a particular interface, or whether a design works for customers? That is a more useful starting point than choosing a research label.
Not sure which approach fits?
A 30-minute conversation with Matt about how the audit works and whether it fits your business.