Authority Bias

SKILL.md

---
name: authority-bias
description: "Activate when: someone says 'should we trust the expert on this?', 'they're a professor/CEO/MD so they must be right', 'I don't want to push back on them', 'we deferred to the board and it blew up', or is evaluating a charismatic founder, assessing due diligence on a high-credential deal, or building a team where senior voices dominate.
Do NOT activate when: the authority is a verified domain expert on the exact question at hand and the decision is time-critical; or when the user is asking a general persuasion question with no authority dynamic involved."
---

# Authority Bias

## Overview

**Authority bias** is the automatic tendency to comply with directives from authority figures — often overriding one's own judgment, ethics, or evidence. It operates beneath conscious deliberation: people substitute the authority's judgment for their own rather than weighing it.

Milgram (1963) showed 65% of ordinary adults administered apparent 450V shocks when instructed by a lab-coated experimenter — against expert predictions of 1-2%. Cialdini (1984) systematized three authority triggers: titles, attire, and trappings — all of which fire regardless of actual expertise.

Key distinction: **positional authority** (CEO, board chair, VC partner) vs. **domain expertise** (demonstrated track record on this specific question type). The bias treats them as identical. The skill does not.

Composes with [`social-proof`](../social-proof/SKILL.md), [`reciprocity`](../reciprocity/SKILL.md), [`critical-thinking`](../critical-thinking/SKILL.md), [`signaling-games`](../signaling-games/SKILL.md), [`dunning-kruger`](../dunning-kruger/SKILL.md).

## When to Use

- Boards, investment committees, due diligence on high-credential founders
- Medical or technical decisions where expert opinion dominates discussion
- Org decisions where senior voices suppress dissent; 360-feedback design
- Negotiations where counterparty leverages credentials or position

**Not when:** authority is verified domain expert on the exact question and speed matters.

## Coaching Novices (Adaptive Front Door)

- **Engine mode:** concrete case → run The Process directly.
- **Coach mode:** unfamiliar or no case → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. One-line: before deferring, ask whether they're a genuine expert on this specific question and whether their reasoning holds up independently.
2. Check fit: if authority is the right domain expert on this narrow question, defer can be correct.
3. Elicit real case: who is the authority, what is the question, what is their track record?
> **[WAIT — do not advance until user responds]**
4. Run S1-S5 one step at a time with their input.
> **[WAIT — do not advance until user responds]**
5. Close: name the insight — calibrated weighting + structural counters if relevant.
> **[WAIT — do not advance until user responds]**

## The Process

**S1 — Identify:** Authority (person/institution) · question/decision · authority signals (title, attire, credentials) · pressure to defer.

**S2 — Expertise vs. positional:** Actual track record on this question type? Positional (CEO, chair) or domain expertise (years operating here)? Would a peer expert agree?

**S3 — Examine reasoning:** Is the reasoning sound independent of who's stating it? Are logical gaps being filled by authority signals?

**S4 — Check for dysfunction:** Is dissent suppressed? Are decisions justified by "X said so"? Is positional authority conflated with domain expertise?

**S5 — Cialdini defense:** (Q1) Genuine expert on this specific question? (Q2) Reasoning holds under independent scrutiny? Both Y → appropriate weight. Either N → discount signal, demand evidence.

**S6 — Structural counter (if you are the authority):** Explicitly invite dissent ("give me 3 reasons against") · separate suggestions from directives · install red team / premortem.

## Output: Authority-Bias Analysis
```
Authority: | Question: | Signals: | Pressure to defer:
Domain expertise (track record): | Positional: | Independent expert:
Reasoning: | Independent assessment: | Gaps:
Cialdini Q1: Y/N | Q2: Y/N | Calibrated weighting:
Structural counter: | Decision + documentation:
```

*→ Method in Action: [Milgram 1963 + Cialdini Systematization + Theranos/FTX](examples/milgram-1963-cialdini-systematization-theranos-ftx.md)*

## Pack: Authority-Bias Application Patterns

| Situation | Defensive question |
|---|---|
| Investment in startup (CEO / VC brand) | Have they demonstrated this specific business model works? |
| Board member's opinion | Is this question actually in their domain expertise? |
| Medical recommendation | What's the evidence base, independent of the white coat? |
| Senior engineer's design decision | Has this approach worked in our specific context before? |
| Founder's product vision | Are users requesting this, or is it founder preference? |

## Applying It Well

- Awareness doesn't prevent deference — structural countermeasures are required.
- When you are the authority, your words are amplified beyond intent; operate accordingly.
- Cialdini defense: (a) genuine expert on this question? (b) reasoning holds independently?

*→ Primary sources: [references/sources.md](references/sources.md)*

## Common Rationalizations

**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**

| Fake move | Reality |
|---|---|
| [D] "They're smart; we should listen" | Smart in general doesn't mean smart on this specific question. Apply the domain test. |
| [D] "Everyone respects them" | Cialdini's social proof reinforcing authority. Both biases compound. Separate them. |
| [D] "They have a great track record" | In what specifically? Apply the question scope check. |
| [D] "It would be rude to push back" | Compliance despite better judgment is the bias operating. Rudeness is not the actual cost. |
| [D] "I'm not in a position to disagree" | If you have contradicting evidence or reasoning, you are. The framing is authority bias self-reinforcing. |
| [D] "If they're wrong, it'll show in due diligence" | Theranos and FTX survived layers of due diligence by leveraging authority to suppress scrutiny. |
| [D] "I'm too junior" | Junior people often have unfiltered observations. Suppressing them is where structural failures occur. |
| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |

## Red Flags

- Decision made primarily because an authority said so, not because the reasoning holds
- Dissent suppressed — junior people silent, mid-managers deferring without pushback
- Due diligence shortened due to authority signals; credentials conflated with domain expertise
- No red team / premortem / devil's advocate on a high-stakes call

## Verification

- [ ] Authority's track record on this specific question examined
- [ ] Positional authority distinguished from domain expertise
- [ ] Reasoning independently examined; at least one dissenting expert sought
- [ ] Cialdini two-question defense applied
- [ ] If org: psychological safety mechanisms in place
- [ ] If you are the authority: structural dissent-encouragement operational
- [ ] Decision documented with reasoning, not just authority attribution

*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*