> 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.md). # Cognitive Bias Cognitive Biases are systematic patterns of deviation from norm or rationality in judgment. They are mental shortcuts that the brain uses to process information quickly and efficiently. While these shortcuts are useful for fast decision-making, they can lead to errors and distorted perceptions of reality. In User Experience (UX) design, understanding cognitive biases is crucial because they profoundly influence how users perceive, interact with, and make decisions about digital products. A good UX designer anticipates and accounts for these biases to create interfaces that are clear, persuasive, and user-friendly. #### Why Biases Matter in UX Cognitive biases can dictate many aspects of a user's interaction: * **Perception of Value:** Biases affect whether a user thinks a product is worth the price or the effort to use. * **Navigation & Discovery:** They influence what users pay attention to on a screen and which paths they choose to take. * **Trust & Credibility:** Biases shape how quickly a user trusts a website, app, or piece of information presented to them. * **Decision-Making:** They drive choices, from clicking a specific button to completing a purchase. By intentionally designing with these biases in mind, you can guide users toward desired actions, minimise friction, and create a more satisfying experience. **Anchoring Bias** The tendency to rely too heavily on the first piece of information offered (the "anchor") when making decisions. *Example: Show a high original price (the anchor) struck out next to a lower sale price to make the sale price seem like a much better deal.* **Confirmation Bias** The tendency to search for, interpret, favour, and recall information in a way that confirms or supports one's prior beliefs or values. *Example: In search or filtering, showing results or suggestions that align with a user's past behaviour or stated preferences (e.g., "People who bought this also bought...").* **Loss Aversion** The psychological tendency for losses to have twice the impact on people as equivalent gains. People prefer avoiding losses over acquiring equivalent gains. *Example: Framing features as things a user will lose if they cancel a service ("Don't lose access to...") rather than things they will gain if they sign up.* There are dozens of cognitive biases that shape how we think and make decisions, often without us realising. Here are some of the most influential ones, especially in business, strategy, and everyday judgment. #### Common Cognitive Biases in Decision-Making * **Confirmation Bias**: Tendency to seek out or interpret information in a way that confirms our existing beliefs. * **Anchoring Bias**: Relying too heavily on the first piece of information encountered (the "anchor") when making decisions. * **Availability Heuristic**: Overestimating the importance of information that comes to mind easily, often because it's recent or vivid. * **Loss Aversion**: Preference to avoid losses rather than acquire equivalent gains; losing €100 feels worse than gaining €100 feels good. * **Overconfidence Bias**: Overestimating our own abilities, knowledge, or control over outcomes. * **Status Quo Bias**: Favouring the current state of affairs and resisting change, even when alternatives may be better. * **Framing Effect**: Decisions are influenced by how information is presented e.g., "90% survival rate" vs. "10% mortality rate." * **Endowment Effect**: Valuing something more simply because we own it. * **Bandwagon Effect**: Adopting beliefs or behaviours because many others do "everyone's doing it." * **Hindsight Bias**: Believing, after an event has occurred, that we "knew it all along." * **Dunning-Kruger Effect**: People with low ability at a task overestimate their ability, while experts may underestimate theirs. These biases can creep into everything from product development to hiring decisions to personal relationships. #### Business Examples & Strategic Implications | Bias | Description | Business Scenario | Impact | | ------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | | [**Sunk Cost Fallacy**](/cognitive-tools/ux-laws-principles/concepts-and-models/cognitive-bias/the-sunk-cost-fallacy.md) | Continuing a project due to past investment, even if future returns are poor | Persisting with a failing product because of prior R\&D spend | Wasted resources, delayed pivot | | **Confirmation Bias** | Seeking info that supports existing beliefs | Ignoring negative user feedback because it contradicts internal assumptions | Poor product-market fit | | [**Anchoring Bias**](/cognitive-tools/ux-laws-principles/concepts-and-models/cognitive-bias/anchoring-principle.md) | Overreliance on initial data or numbers | First price quoted in negotiations sets the tone | Skewed pricing decisions | | [**Authority Bias**](/cognitive-tools/ux-laws-principles/concepts-and-models/cognitive-bias/authority-principle.md) | A person's tendency to comply with people in positions of authority | Following a flawed strategy because it was proposed by a senior executive or "HiPPO" (Highest Paid Person's Opinion). | Reduced innovation and critical thinking; teams may ignore data in favour of pleasing leadership. | | **Availability Heuristic** | Judging based on easily recalled examples | Overestimating risk due to recent news (e.g., cyberattack) | Misallocation of security budget | | **Loss Aversion** | Fear of losses outweighs desire for gains | Avoiding innovation due to fear of cannibalizing existing products | Missed growth opportunities | | **Overconfidence Bias** | Overestimating one’s knowledge or control | Launching without proper market testing | Failed product rollout | | **Status Quo Bias** | Preference for current state | Not adopting new tools or workflows | Stagnation, inefficiency | | **Framing Effect** | Decisions influenced by how info is presented | “95% success rate” vs “5% failure rate” in marketing | Misleading perception | | **Endowment Effect** | Overvaluing owned assets | Overpricing a legacy product | Reduced competitiveness | | **Bandwagon Effect** | Following the crowd | Copying competitors’ features without validation | Diluted brand identity | | **Hindsight Bias** | Believing outcomes were predictable | “We knew that campaign would fail” after poor results | Blame culture, poor learning | | **Dunning-Kruger Effect** | Low-skilled individuals overestimate ability | Junior team member dismisses expert advice | Risky decisions, team friction | #### How to Use This in Practice * **Team Workshops**: Run a "Bias Spotting" session where teams reflect on past decisions and identify which biases may have influenced them. * **Strategy Reviews**: Use this table as a checklist when evaluating new initiatives. Ask "Are we falling into any of these traps?" * **Leadership Coaching**: Help managers recognise bias in hiring, performance reviews, and resource allocation. #### Further Reading {% embed url="" %} {% embed url="" %} {% embed url="" %} --- # 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.md?ask=&goal= ``` `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.