Cognitive Principles

Barrier Analysis

Before designing any conversion solution, you must diagnose exactly what prevents the target behaviour — generic friction reduction fails when the actual barriers are specific and unaddressed.

Where it comes from

It's a diagnostic principle articulated by Maurice Münster: effective behaviour change starts not with designing solutions but with identifying what specifically stops the behaviour you want. The barriers are usually concrete, often unexpected, and rarely the generic ones designers reach for by default.

Why it matters for your website

Münster's barrier analysis principle says that effective behaviour change begins not with solution design but with diagnosis: what specifically prevents the behaviour you want? Generic principles (reduce friction, add social proof, simplify copy) address generic barriers. Real pages have specific audiences with specific doubts — and those doubts are often not what designers assume. The audit implication is a diagnostic question: for each conversion step on this page, has the team identified the specific belief or obstacle that stops visitors here — and does the design directly address it? A page optimised against assumptions is often a page optimised against the wrong problem.

Generic fixes address generic barriers. 'Reduce friction', 'add social proof', 'simplify the copy' are answers to problems you haven't yet diagnosed — and a real page has a specific audience stuck for specific, often surprising reasons. Optimising against assumptions usually means optimising the wrong thing.

The discipline is to ask, for each conversion step, what specific belief or obstacle stops people here — and then to check whether the design addresses that, rather than a barrier the team imagined. The actual blocker is frequently not what designers assume, which is why the diagnosis has to come before the solution.

Wrong vs right

Wrong

Applying a checklist of generic best practices to a stalling page without diagnosing why visitors actually drop off.

Right

Identifying the specific doubt or obstacle at each step first, then designing directly against it.

Wrong

Assuming the barrier is price when it's actually trust — and discounting, to no effect.

Right

Diagnosing the real barrier (say, a security worry) and addressing that specific concern.

Wrong

Optimising a step against the team's assumptions about visitors rather than their actual beliefs.

Right

Grounding the fix in evidence of what genuinely stops this audience at this step.

Understanding Barrier Analysis

Barrier analysis is the principle that behaviour change should begin with diagnosis, not solution design. Before deciding how to lift a conversion, you identify what specifically prevents the behaviour you want at each step. The barriers that matter are concrete and particular — this audience, this doubt, this obstacle — and they're frequently not the ones a designer would assume from the outside.

This is a corrective to a common failure mode: applying generic remedies to undiagnosed problems. 'Reduce friction', 'add social proof', 'simplify the copy' are all sound in the abstract, but they address generic barriers. A page that stalls does so for a specific reason, and a generic fix aimed at the wrong barrier leaves the real one untouched.

The practical form is a diagnostic question asked of every conversion step: what specific belief or obstacle stops visitors here, and does the design directly address it? A page optimised against assumptions is often a page optimised against the wrong problem. Getting the diagnosis right is what makes the solution work. It connects to objection handling, hypothesis-first design, and the distinction between vanity and actionable metrics.

How Kweri checks it

Barrier analysis is fundamentally a diagnostic discipline, and Kweri supports it more as a prompt than a measurement. It can flag conversion steps that appear to lack obvious barrier-handling — a checkout with no reassurance, an ask with no objection addressed — and pose the diagnostic question. But identifying the *specific* belief that stops your particular audience requires knowledge of your users and ideally direct research, which a static review can't supply. So Kweri raises where barriers seem unaddressed and prompts the right question, while the real diagnosis is yours to make.

FAQ

What is barrier analysis?

Barrier analysis is the practice of diagnosing what specifically prevents a desired behaviour before designing a solution. It holds that effective conversion work starts with identifying the real, specific obstacles — not applying generic best practices.

Why do generic conversion fixes often fail?

Because they address generic barriers, while a real page stalls for specific, often unexpected reasons. 'Reduce friction' or 'add social proof' won't help if the actual obstacle is something else entirely that goes undiagnosed.

How do I do barrier analysis?

For each conversion step, ask what specific belief or obstacle stops visitors there, ground the answer in evidence rather than assumption, and check whether the design directly addresses that barrier. Diagnose before you design.

Why are assumed barriers a problem?

Because the real blocker is frequently not what designers assume. A page optimised against assumed barriers is often optimised against the wrong problem, leaving the actual obstacle in place while effort goes elsewhere.

How is barrier analysis related to objection handling?

Objection handling is one application: once you've diagnosed the specific doubt stopping visitors, addressing it directly is how you remove the barrier. Barrier analysis is the diagnosis; objection handling is part of the response.

Related principles

Attribution & sources

Identified by Maurice Münster. Catalogued from Conversion psychology (Münster).

A diagnostic principle for conversion design articulated by Münster; there's no single canonical web source.

See Barrier Analysis on your own site

Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.

Run a free audit →