Anchoring Bias.

01Overview

Anchoring bias is the brain's habit of grabbing the first plausible number it sees and dragging every later judgment toward it. The anchor doesn't have to be relevant. It doesn't even have to be plausible. Show someone a price, an estimate, or a slider default, and that number will quietly shape what they think anything else is worth.

This is the bias most directly under designers' fingertips. Defaults, placeholders, "from $" pricing, the position of the most expensive tier — these aren't neutral choices. They're anchors.

02Detailed explanation

The classic demonstration is almost rude. Researchers spin a wheel rigged to land on 10 or 65. They ask participants whether the percentage of African nations in the UN is higher or lower than that number, then ask them to estimate. People who saw 10 averaged 25%. People who saw 65 averaged 45%. The wheel was visibly random. It didn't matter.

The effect shows up almost everywhere a quantity is judged under uncertainty:

• Asking people for their phone number's last two digits before estimating the year an event occurred — estimates correlate with the digits.
• Setting a "suggested tip" of 25% vs 18% shifts the tipping distribution measurably.
• Showing a strike-through "$199 was $349" makes $199 feel cheap, even when $199 is the standard price.

03Why it exists

Most quantitative judgments in life are made without reliable reference points. How much should a coffee subscription cost? How long should onboarding take? How many designers does a team need? Without a benchmark, the brain reaches for whatever is nearby — and treats it as a starting point to adjust away from.

Adjustment, it turns out, is lazy. People stop adjusting as soon as the answer becomes plausible — which means estimates land much closer to the anchor than they should.

04Effects on users

• A $79 tier next to a $299 tier feels reasonable. The same $79 tier next to a $19 tier feels expensive.
• A donation form with suggested amounts of [$5, $10, $25] raises a different average than [$25, $50, $100] — even from the same audience.
• A "typical time: 2 minutes" label on a long form makes the form feel betraying when minute three arrives.
• A pre-filled estimate field nudges users away from the truth and toward the placeholder.

05Effects on designers & teams

Anchoring isn't only something you do to users. It happens in the workshop too:

• The PM's estimate. "I think this is a two-week thing." The number is now in the room. Every engineer's estimate adjusts away from two, not from zero.
• The first comp. The first design shown in a critique sets the visual anchor. Subsequent options get evaluated as variations on it, not as independent ideas.
• The roadmap deadline. A specific Q3 launch date — even one written without confidence — becomes the gravity the whole quarter bends around.

06Introspective view

Look inward. Anchoring is not only something you place in an interface — it is something that happens inside the room before a single pixel ships. The first number spoken, sketched, or typed becomes the gravity well your team adjusts around, often without anyone agreeing it should.

From an introspective perspective, the question is not "what anchor should we show users?" but "what anchor am I already carrying into this decision?" Competitive pricing you saw over breakfast, a stakeholder's offhand timeline, the first wireframe on the wall — each can narrow what you consider possible before you have tested anything.

07Extrospective view

Look outward. Users rarely arrive with a clean mental spreadsheet. They meet your product with uncertainty — about price, effort, risk, and value — and the first number or label they encounter gives their brain somewhere to start adjusting from.

From an extrospective perspective, anchoring is a property of the interface itself: tier order on a pricing page, suggested amounts on a donation form, a struck-through "was" price, the default position of a slider. Users are not foolish for being pulled toward these cues; they are doing exactly what brains do under incomplete information. Your job is to decide whether each anchor helps people decide well — or merely decide quickly in your favour.

08Practical takeaways

• Choose your anchor on purpose. Every default value, suggested amount, and "from $" is an anchor. Audit them as deliberately as you'd audit copy.
• Position your real product, not your decoy. If your middle tier is what most users should pick, the anchor — top tier price, struck-through "was" price — should make it feel like the right choice, not a discount.
• Estimate independently. In planning, have everyone write their estimate before talking. The "talking" version is anchoring poker.
• Show options side-by-side at the same time. Anchoring is strongest sequentially. Parallel presentation softens it.
• Place numbers carefully in research. "How much would you pay for this — up to $50?" is not a price test. It's an anchor test.

09Design examples

10Ethical risks

Anchors are the single most exploitable bias in modern interface design. Strike-throughs that never reflected a real price, "starting at" rates buried in fine print, donation defaults engineered to extract — these are the loudest dark patterns regulators have started fining, and they all rest on anchoring.

A useful self-test: would I show this design to the user three weeks later, and would they thank me for it? If the anchor only works because the user doesn't notice it, you're not designing. You're skimming.

11Related biases