Usability Testing

Conversion & UX

Also: User Testing · UX Testing

What it doesWatches real people use your site
Not a surveyObservation, not opinion
Sample sizeSmall groups reveal most issues
Watch forTesting on the wrong people

Quick definition

Usability testing is watching real people try to complete a task on your website or app, then noting where they hesitate, get confused or give up. It's an observational method, not a survey, and it's designed to surface friction that analytics data alone can't explain.

How it varies across Australia

Most Australian businesses skip usability testing entirely and rely on analytics and gut feel instead. The gap shows up in checkout and form-heavy flows, where a handful of watched sessions routinely surface issues that months of heatmap data never flagged.

See conversion and UX benchmarks across Australian industries

What it actually means

Analytics is a rear-view mirror. It shows you the drop-off point on your checkout page but says nothing about why someone abandoned there. Usability testing fills that gap by putting a real person in front of your site, giving them a task, and watching what they actually do rather than what they say they'd do.

The format is simple. Recruit a handful of people who resemble your actual customers. Give them a specific task, like 'find and add a product to cart' or 'sign up for the newsletter'. Watch, don't help. Note every hesitation, every wrong click, every moment they say 'I'm not sure what this means'.

The insight almost never matches what the internal team expected. A button that seemed obvious to the designer is invisible to a first-time visitor. A form field that seemed harmless triggers three people to abandon. This is why usability testing pairs well with conversion rate work: it explains the mechanism behind the number, not just the number itself.

Most teams assume this requires a lab, a facilitator and a budget line. It doesn't. Five people and forty minutes will surface most of your worst problems.

Analytics tells you where people dropped off. Usability testing tells you why, and the why is usually more embarrassing than expected.

How it shows up

Usability testing shows up as recorded sessions, moderator notes, and a shortlist of friction points ranked by how many participants hit them. It also shows up indirectly wherever a redesign ships without it: a spike in support tickets asking 'how do I do X', a form field with an unusually high abandonment rate, or a feature nobody uses because nobody understood what it did. The absence of usability testing is often more visible than its presence.

The Australian context

Recruiting for usability testing in Australia is straightforward for consumer products but can be genuinely hard for niche B2B categories, given the smaller pool of qualified participants. Many Australian teams solve this by testing with adjacent-industry participants or running sessions with existing customers who fit the target persona for a new feature, even if they're not ideal for testing the core flow.

Where people get this wrong

Asking participants what they think instead of watching what they do.People are unreliable narrators of their own behaviour. What someone says they'd click and what they actually click are frequently different things.
Treating one round of testing as final.A single session catches surface issues. Recurring testing across releases catches the issues that only appear once the obvious ones are fixed.
Only testing the happy path.Real users hit edge cases, error states and unexpected navigation choices. A test script that only covers the ideal flow misses most of where people actually get stuck.

Related terms

Common questions

How many people do I need for usability testing?

Five is the commonly cited number, and it holds up in practice. Five well-chosen participants typically surface most of the major usability issues. Beyond that, additional testers mostly repeat findings rather than reveal new ones.

Is usability testing the same as A/B testing?

No. Usability testing is a small qualitative exercise that explains why people struggle with something. A/B testing is a large quantitative exercise that measures which of two versions performs better. They answer different questions and work well together.

Can I do usability testing without a budget?

Yes. Recruit five people who fit your target persona, give them one task, watch them complete it over a video call, and take notes. Paid tools and labs make the process smoother but aren't required to get useful results.

When should usability testing happen in a project?

Ideally before launch, on prototypes or wireframes, so problems get caught before development. It's also valuable after launch on live pages, especially ones with unexplained drop-off in the conversion funnel.

Debrief

Get the next one

No spam. No fluff. Just the next article, straight to your inbox.

Keep exploring

About New Rebellion

New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.

How we think →