Menu

UX

Interaction Audit

A practical UX quality method for reviewing how interactive elements behave across screens, states, and flows.

How to run an interaction audit to identify inconsistent behaviours, reduce friction, and improve predictability across your product.

4 min read

What it is

An audit is a UX method used to evaluate the , , and effectiveness of interactive elements within a product.

It involves reviewing components such as buttons, links, menus, forms, gestures, transitions, and mechanisms to ensure they behave predictably and support user goals.

The focus is on identifying inconsistencies, points, and issues in .

Key takeaway

The goal is to optimise user flows, reduce errors, and create a cohesive experience.

When to use it

Use this method when quality matters.

It is most useful when:

multiple teams or designers have contributed to the interface
redesigning or scaling a product
users experience errors, confusion, or inefficiency
onboarding new users or features
preparing for usability testing or release

It is less useful when:

the interface has minimal interactive elements
interactions are simple and self-evident
Interaction audits are often used alongside UI consistency reviews, usability testing, and heuristic evaluations.

How to run it

Set up properly

Be clear on the scope (which screens, components and states) and what correct is for each type of element.

Include every state: default, hover, focus, active, disabled, loading, error, empty. Most inconsistency lives in the states nobody designed.

Run the method

An audit catalogues every interactive element and checks each behaves as it should. It is systematic and dull, and it finds things no journey-based review will.

  1. Catalogue all interactive elements across the scope, recording where each appears.
  2. Test each for expected and , including what happens on slow connections.
  3. Check across similar elements and screens. The same control behaving differently in two places is worse than either alone.
  4. Note , errors and confusion, with the specific element and state.
  5. Rate severity and propose a corrective action for each rather than only listing the fault.

Compare like with like. The finding is usually not that a control is bad but that three of it exist and each behaves slightly differently.

Capture and make sense of it

The value comes from systematic coverage. After the audit, document:

  • Every element failing its expected , with the state
  • Inconsistencies between elements doing the same job
  • Missing states, especially loading, empty and error
  • Severity and a proposed fix for each

Use this to raise baseline quality and to the case for a . Most findings resolve into a handful of shared components.

Key takeaway

Use this to streamline interactions and improve the user experience.

What to look for

Focus on:

Predictability: do elements behave as users expect?
Consistency: are similar interactions uniform across the product?
Feedback: is user action acknowledged appropriately?
Efficiency: can users complete tasks without unnecessary effort?
Errors: confusing or broken interactions

Where it goes wrong

Most issues come from:

If are unreliable, users lose and .

Auditing screens rather than components, so variants go unnoticed
Skipping states (loading, empty, error, disabled) where most defects live
Recording an inconsistency without saying which version is correct
Testing only the happy path for each control
Producing a list with no severity, which nobody schedules

What you get from it

Done properly, this method gives you:

Every control that behaves other than it should, with its state
The same job being done three different ways
Missing states, which are the commonest omission
Findings that usually resolve into a handful of shared components

Key takeaway

It helps create interfaces that feel reliable and intuitive.

Get in touch

If this sounds like something you need, we can help you audit your interactions to create consistent, reliable, and intuitive experiences that users trust.

No guesswork. No assumptions. Just interactions that work.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is an interaction audit in UX?

It is a method for evaluating the behaviour, consistency, and usability of interactive elements in a product.

When should you use an interaction audit?

During redesigns, pre-launch reviews, or usability optimisation.

What can you audit?

Buttons, links, forms, menus, gestures, feedback mechanisms, and transitions.

Why does interaction consistency matter?

Consistent and predictable interactions reduce user errors, frustration, and cognitive load.

Does an interaction audit improve UX?

Yes. It ensures users can interact confidently and complete tasks efficiently.

Quick take

If interactions feel inconsistent or confusing, users struggle. Audit them to improve usability and flow.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer