Decision-making

Cognitive Bias

A cognitive bias is a systematic error in thinking — a mental shortcut that predictably skews how people perceive information and make decisions.

Core · User Behaviour & Decision System2 research sources
Share
The Müller-Lyer illusion: two equal lines that look different lengths — an illustration of Cognitive Bias.

See it in action

The same screen without and with Cognitive Bias. Watch both sides play out, then compare the outcome.

Leading survey questionQuick survey“How much did you love the new dashboard?”Loved it62%Liked it28%It was OK10%Looks like a hit — but the wording did the work

The question presumes a positive answer and offers no negative option, so the data mostly measures the bias.

Neutral question, balanced scaleQuick survey“How was the new dashboard?”Good38%Neither27%Poor35%A real split — and something worth fixing

Neutral wording and a symmetric scale reveal what people actually think.

What to watch: the same feature, two wordings — and two very different charts.

Do

Design research and flows to counter known biases: neutral wording, balanced options, real behaviour.

Don’t

Assume users (or your team) judge rationally; biases shape both what users do and what you conclude.

Key takeaways

  • Users don't evaluate options neutrally; shortcuts like anchoring, framing and loss aversion shape every choice.
  • Designers have biases too — test assumptions with real behavior data.
  • Use biases to remove friction and help users, never to trick them into choices against their interest.

Quick facts

Also known as
—
Described by
Amos Tversky & Daniel Kahneman
Year
1974
Category
Decision-making

Cognitive Bias explained

A cognitive bias is a systematic pattern of deviation from purely rational judgement. Rather than weighing every option carefully, the brain uses mental shortcuts (heuristics) that are usually fast and useful but predictably wrong in certain situations.

Biases affect both users and product teams. Users are influenced by defaults, framing, anchors and social proof when they decide; teams are influenced by confirmation bias and the false-consensus effect when they interpret research and assume users think like they do.

Understanding biases helps designers reduce friction and help people make choices that match their own goals. Using biases to trick people into decisions they would not otherwise make is a dark pattern, and it damages trust and increasingly breaks consumer protection rules.

Where it comes from

Amos Tversky and Daniel Kahneman introduced the modern study of heuristics and biases in their 1974 Science paper 'Judgment under Uncertainty: Heuristics and Biases', describing representativeness, availability and anchoring. Kahneman later summarised the field for a general audience in Thinking, Fast and Slow (2011).

How it shows up in apps

Every screen where a user decides something — which plan, whether to grant a permission, whether to continue onboarding — is shaped by predictable biases. Diagnosing which bias is at play explains why a 'logical' flow still underperforms, and points to the specific change that will help.

Cognitive Bias examples

Showing an annual plan's price as a monthly equivalent next to the monthly plan changes how expensive each option feels, even though no prices changed.

  • Confirmation bias in research

    A product team that believes a new dashboard is better hears the positive comments in usability sessions and explains away the struggles. Pre-defining success metrics before testing guards against this.

  • Anchoring on a pricing page

    Showing an annual plan's monthly-equivalent price next to the monthly plan anchors the comparison, making the annual option feel like clear value.

  • Status quo bias in settings

    Most users never change notification defaults, so whatever the team chooses as the default effectively becomes the experience for the majority.

How to apply Cognitive Bias

  1. Identify the decisions users make in your key flows and ask which shortcuts they are likely to rely on.
  2. Design defaults, framing and ordering to help users reach outcomes they would endorse on reflection.
  3. Check your own team's assumptions against data; write hypotheses and success criteria before running research.
  4. Avoid manipulative patterns such as hidden costs, fake urgency or confirm-shaming.
  5. Review high-stakes flows (payments, privacy, cancellations) for fairness and regulatory compliance.

Want Cognitive Bias checked in your own product? Our saas ux audit evaluates it alongside the other principles that shape how users decide, onboard and stay.

Common mistakes

  • Treating biases as tricks to boost short-term conversion, which erodes trust and invites regulatory risk.
  • Assuming users are irrational in general; biases are predictable and situational, not a sign that people cannot decide well.
  • Forgetting that the team's own biases shape research, prioritisation and design reviews.

How to measure it

Run controlled experiments that change one decision factor at a time (default, order, framing) and measure both the immediate choice and later outcomes such as satisfaction, refunds, churn or complaints. Healthy uses of biases improve both; manipulative ones raise short-term numbers while hurting long-term ones.

Frequently asked questions

What is Cognitive Bias?

A cognitive bias is a systematic error in thinking — a mental shortcut that predictably skews how people perceive information and make decisions.

Where does Cognitive Bias come from?

Amos Tversky and Daniel Kahneman introduced the modern study of heuristics and biases in their 1974 Science paper 'Judgment under Uncertainty: Heuristics and Biases', describing representativeness, availability and anchoring. Kahneman later summarised the field for a general audience in Thinking, Fast and Slow (2011).

How does Cognitive Bias apply to app design?

Every screen where a user decides something — which plan, whether to grant a permission, whether to continue onboarding — is shaped by predictable biases. Diagnosing which bias is at play explains why a 'logical' flow still underperforms, and points to the specific change that will help.

How many cognitive biases are there?

Researchers have described well over a hundred, but a smaller set (such as anchoring, loss aversion, framing, defaults, social proof and confirmation bias) explains most of what matters in product design.

Is designing for cognitive biases ethical?

It can be. Designing so that people's natural shortcuts lead them to choices that serve their interests is ethical; exploiting biases against users' interests is a dark pattern and may be illegal under consumer protection laws.

How do you measure Cognitive Bias in a product?

Run controlled experiments that change one decision factor at a time (default, order, framing) and measure both the immediate choice and later outcomes such as satisfaction, refunds, churn or complaints. Healthy uses of biases improve both; manipulative ones raise short-term numbers while hurting long-term ones.

Sources

  1. Tversky, A. & Kahneman, D. (1974). Judgment under uncertainty: Heuristics and biases. Science, 185(4157). Find on Google Scholar ↗
  2. Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux. Find on Google Scholar ↗

View all 60 laws of UX

Keep exploring

Cognitive Bias in practice

Keep exploring

Certifications that test it

Pass it on

Teach this to your team

Share it before your next design review — a shared vocabulary makes product decisions faster.

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free certification

Can you apply Cognitive Bias under pressure?

Test it in 18 real product scenarios in the free Product Design Science test. Score 70% and earn a founder-signed certificate anyone can verify.

  • Credential ID
  • QR verification
  • LinkedIn-ready
Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 74 pages

Get Laws of UX by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy

Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 90 pages

Get 100+ Paywalls, Decoded by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy