Lesson 3.20 · StrategyGuide · 10 min readFree · No signup

Backfire Effect: challenging beliefs can make them stronger

Part of the Psychology of Design learning path. The cognitive biases and psychology principles behind every click, scroll, and conversion.

L3 · How people act over time · Lesson 20 of 2610 min read for this one

What you'll understand by the end of this lesson

  • Why directly challenging a visitor's belief can entrench it rather than change it
  • Why aggressive competitor comparisons can backfire in marketing copy
  • How to handle objections without triggering defensiveness
  • How reframing works as an alternative to head-on confrontation

The principle in plain English

When someone holds a belief firmly — especially one tied to their identity or self-image — and you present them with evidence that contradicts it, they don't always update the belief. Sometimes they reject the evidence and hold the belief more strongly than before.

This is the Backfire Effect. The psychological mechanism is threat response: correcting a deeply held belief feels like an attack. The person's defensive instincts activate, and rather than considering the evidence on its merits, they work to dismiss or discredit it.

The strength of the effect correlates with how threatening the correction feels. A small factual correction about something neutral produces little resistance. A correction that touches someone's professional identity, political views, or self-perception as competent and intelligent triggers much stronger defensive responses.


A simple example

A founder believes their checkout process is simple and user-friendly. They've built it, they know how it works, they've used it themselves. A CRO consultant shows them session replays of users struggling, fumbling, and abandoning.

Rather than concluding "our checkout needs work," the founder concludes: "those users were confused," "they weren't our target customer," "the tester ran it on a bad day," "the replays are unrepresentative."

The evidence didn't change the belief. In some cases, the confrontation with evidence increased the founder's conviction that the checkout is fine — because the alternative (accepting that they built something poor) is threatening.


How the Backfire Effect appears in CRO and marketing

Competitor comparisons that go too far

Comparison copy — "Switch from Tool X. Unlike them, we don't charge for [feature]" — is common in B2B SaaS. When done with restraint, it works. When done aggressively, it can backfire.

A visitor who has invested time and money in a competitor's tool has a belief attached to that choice: "I picked a good tool." Aggressively attacking the tool they chose is an indirect attack on their judgment. The defensive response is to dismiss the attack rather than evaluate it.

Restrained comparisons ("Here's how we handle [specific problem]") invite evaluation. Aggressive ones ("Tool X is overpriced and under-featured") invite defence.

When writing comparison copy, focus on a specific capability difference rather than a broad quality judgment. "We process payments in 2 seconds vs the industry average of 8 seconds" invites factual evaluation. "Competitors are slow and expensive" invites rejection. Specific claims give people something concrete to evaluate; broad dismissals trigger protective defensiveness.

Objection handling that triggers resistance

A classic CRO technique is to surface and address objections directly on the page: "You might be wondering if this is worth the cost…" When done well, this technique builds trust by showing the brand understands visitor concerns.

Done badly — where the objection is named but then dismissed ("Some people worry about price, but they're wrong to") — it can trigger the Backfire Effect. The visitor who has that concern now feels their worry has been invalidated, not addressed. That dismissal can entrench the concern rather than dissolve it.

The difference is: acknowledging the concern genuinely, then providing specific evidence, rather than dismissing it.

Your copy's implicit criticism of the visitor

Some landing pages are written in a way that implies the visitor's current approach is wrong: "Most teams are wasting hours on this every week." "You're probably still doing X the hard way." These framings call out a belief or behaviour the visitor may hold and name it as a failure.

This can work — naming a pain point is valid. But when the tone tips from empathy ("we know this is hard") to criticism ("you're doing it wrong"), the defensive response kicks in. The visitor who is doing X the old way may feel attacked, not understood.

The Backfire Effect is strongest when beliefs are tied to identity. Be especially careful when your copy implicitly criticises a professional decision a visitor has made — their choice of tool, their current workflow, or their team's approach. These are identity-adjacent. Criticism feels personal even when it's framed as generic.


The CRO audit

Look at your landing pages and marketing copy and ask:

1. Where does your copy challenge a visitor's existing belief?

This isn't automatically wrong — challenging beliefs is often the point of conversion copy. The question is: how threatening is the challenge? Is it framed as an attack or as new information?

2. How do you handle objections on the page?

Find the objections you name. For each one, check whether you genuinely acknowledge it and provide evidence, or whether you name it and dismiss it. The latter can backfire.

3. If you have comparison copy, is it specific and factual?

Replace broad quality judgments ("they're worse") with specific capability comparisons ("we do X, they don't"). Give the visitor something concrete to evaluate rather than a claim that triggers defensive evaluation of their existing choice.



Q1

A SaaS company writes this headline: 'Still using spreadsheets? You're leaving money on the table.' A visitor who uses spreadsheets reads this. What psychological response might this trigger?

Think about this

You know how to avoid triggering defensiveness. But what about a different distortion — assuming other people think the same way you do? Next — why product teams build for themselves instead of users, and how to catch this bias before it shapes your decisions.