Friction Audit

A friction audit is a manual or semi-automated review process where a researcher walks through a funnel step-by-step — often combined with session recordings, heatmaps, or user testing — to flag anything that makes the experience harder than it needs to be. Unlike a quantitative funnel analysis, which tells you where users drop off, a friction audit tries to explain why, surfacing candidate hypotheses for future A/B tests.

CRO teams run friction audits before investing in a testing roadmap because they turn vague goals ('improve checkout conversion') into specific, testable hypotheses ('users abandon at the address form because it asks for phone number before showing shipping cost'). Common friction sources include unclear error messages, unnecessary form fields, unexpected costs revealed late, slow page loads, and confusing navigation.

As an example, a SaaS signup audit might reveal that users hesitate on a step asking for a job title and company size before they've seen any product value — the audit flags this as a friction point, leading to a hypothesis test that moves those fields later or makes them optional, followed by an A/B test to validate the fix quantitatively.

Friction audits are inherently qualitative and subjective, so most teams pair them with quantitative signals (drop-off rates, rage clicks, form abandonment data) to prioritize which friction points are worth the engineering effort to fix and test, rather than acting on audit findings alone.