> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/ux-laws-principles/concepts-and-models/cognitive-bias/anchoring-principle.md).

# Anchoring Bias

{% hint style="info" %}
AKA Anchoring Principle, Anchoring Effect, Anchoring, Anchor Bias
{% endhint %}

The anchoring principle is a psychological heuristic that describes our tendency to rely too heavily on the first piece of information offered when making decisions. In the context of user experience, this initial piece of information acts as a mental hook, or an anchor, that sets the tone for all subsequent judgements. Once an anchor is set, other judgements are made by adjusting away from that point, which often leads to a bias because users rarely move far enough away from the original value.

You will frequently see this method applied in pricing tables where a premium option is listed first. By showing a high price point at the start, every other price shown afterwards seems significantly more affordable by comparison, even if those prices are objectively high. Designers also use anchoring in search filters or suggested donation amounts. If a website suggests starting a donation at $50, a user might feel that $20 is a small contribution, whereas if the anchor had been $5, that same $20 would feel quite generous.

Beyond just numbers, anchoring can influence how users perceive the quality or speed of a service. For example, if a loading screen provides a high initial estimate for a download time, the user feels a sense of relief and satisfaction when the actual progress bar moves faster than that first expectation. It is a powerful tool for managing expectations, but it must be used ethically. If the anchor is too far removed from reality, it can lead to frustration or a total loss of trust in the interface.

<figure><img src="/files/11quOriyQWCK6o9r4ldx" alt=""><figcaption><p>Image by <a href="https://thedecisionlab.com/biases/anchoring-bias">The Decision Lab</a></p></figcaption></figure>

**Example 1**

My husband and I were car shopping and found a used BMW that looked pristine and had only 10,000 miles on it. The price was shockingly low, only €2,000. We had to have it. Driving home, we smiled from ear to ear about our shiny used car, unknowing it would fall apart within 18 months. We had focused so much on the price and vehicle make, that we did not consider the possible issues (such as rusted parts in old, unused cars). This is anchoring bias at work.

**Example 2**

Imagine you're in a negotiation for a salary increase at work. You go into the meeting with a desired salary in mind, let's say €50,000 per year. Your boss starts the discussion by offering you a raise of €30,000 per year, a significant increase from your current salary. The initial offer of €30,000 becomes the anchor point for your salary negotiations. Because of the anchoring effect, you may find it challenging to ask for the €50,000 you originally had in mind. Instead, you might feel inclined to negotiate from the €30,000 base. In the end, you might agree on a salary of €40,000, which is significantly lower than your initial target but still higher than your current pay. In this scenario, the anchoring bias influenced your perception of what was a reasonable salary increase, causing you to settle for less than you initially aimed for.

**Example 3**

Imagine you're at a high-end restaurant and you're perusing the wine menu. The menu offers a range of wines, with prices that vary from €20 to €500 per bottle. You're not a wine connoisseur, so you're not quite sure which one to choose. However, you notice that there's a special "wine of the month" listed at €250 per bottle. This high price tag becomes the anchor point for your perception of what's expensive. Now, when you look at the rest of the wine options, you may consider the €100 bottle as a reasonable and even affordable choice in comparison to the €250 bottle, even though it's still quite expensive in absolute terms. You might end up ordering the €100 bottle, influenced by the anchoring effect, even though you initially intended to spend no more than €50 on wine. In this example, the initial high anchor price of the "wine of the month" influenced your perception of what constitutes an expensive wine, leading you to spend more than you originally intended.

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=ja4Sp71PFm8>" %}

{% embed url="<https://www.youtube.com/watch?v=ovhuYznC_38>" %}

#### Further Reading

{% embed url="<https://www.nngroup.com/articles/anchoring-principle/>" %}

{% embed url="<https://thedecisionlab.com/biases/anchoring-bias>" %}

{% embed url="<https://www.interaction-design.org/literature/topics/anchoring?srsltid=AfmBOoqypKHTimskRpLAgjeQM08LRZ42cR0O2e1JGukL0I7HXyVi9cNE>" %}

{% embed url="<https://www.creativeo.co/post/the-anchor-bias-principle-in-marketing-with-examples>" %}

{% embed url="<https://psychologycorner.com/neuromarketing-and-behavioral-economics/the-anchoring-principle/>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/concepts-and-models/cognitive-bias/anchoring-principle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.