Behavioral Decision-Making and Cognitive Biases

Behavioral Decision-Making & Cognitive Biases

The descriptive account of judgment and decision-making: how people actually decide, not how they should. Use it to read why a customer, buyer, or stakeholder made a seemingly irrational choice, to ethically shape the decision environment, and to catch bias in your own forecasts and recommendations.

Installed as a Claude Code skill with four on-demand reference files (not duplicated here): references/biases-catalog.md (full heuristics-and-biases catalog with canonical experiments + TAM application notes), references/choice-architecture.md (defaults, EAST, MINDSPACE, sludge vs nudge vs boost, choice overload, ethics of influence), references/debiasing-and-application.md (debiasing procedures + worked operator scenarios), and references/replication-status.md (what survived vs what is contested/failed, with citable sources — read before citing any effect externally).

Descriptive vs normative: keep them separate. This skill is descriptive (the psychology of real decisions). For the normative side, computing the optimal action under constraints (linear programming, decision trees, EVPI, expected-utility maximization), use da-33-prescriptive-analytics. The gap between the two is the subject matter here: people deviate from the normative optimum in systematic, predictable ways.

The honesty rule (read first). Decision/social psychology went through a replication crisis. Several once-famous effects did not survive (power posing, social priming, and ego depletion are contested/failed). The core judgment-and-decision-making findings (anchoring, framing, the disposition effect, present bias, default effects) replicate well; several adjacent social-psych effects do not. Never present a debunked effect as established fact. See references/replication-status.md before citing any effect to a customer or in a written recommendation.

When to reach for this skill

If the task is changing a customer’s behavior over time (adoption, habit, enablement), that’s behavior-change-psychology, not this skill.

Core concepts (the minimum working set)

1. Dual-process theory: System 1 / System 2

Two modes of cognition. System 1 is fast, automatic, associative, affect-laden, and effortless; it produces most snap judgments and most biases. System 2 is slow, deliberate, effortful, and lazy (it endorses System 1 unless prompted). Labels coined by Stanovich & West, popularized by Kahneman (Thinking, Fast and Slow, 2011). Biases are System 1 outputs that System 2 fails to catch.

2. Heuristics & biases (Tversky & Kahneman, 1974, Science)

Mental shortcuts that are “highly economical and usually effective” but produce “systematic and predictable errors.” The working set every operator should recognize: anchoring-and-adjustment (the first number dominates; the single most useful effect in negotiation), availability (judging probability by ease of recall; the loud outage feels likelier than the silent risk), representativeness (stereotype/similarity over base rates; the conjunction fallacy), confirmation bias (the engine behind most bad root-cause calls), hindsight bias (“knew it all along”; corrupts postmortems), overconfidence (90%-confident estimates are right far less than 90% of the time; the planning fallacy), status-quo / default bias, and sunk-cost fallacy (honoring unrecoverable past spend instead of deciding on the margin). Detail and operator scripts: references/biases-catalog.md.

3. Prospect theory (Kahneman & Tversky, 1979, Econometrica)

How people choose under risk, the descriptive replacement for expected-utility theory: reference dependence (outcomes judged as gains/losses from a reference point; whoever sets the reference frames the decision), loss aversion (losses loom larger than equivalent gains; classic estimate ~2x, but CONTESTED, do not state “2x” as universal law), diminishing sensitivity (concave for gains, convex for losses), probability weighting (small probabilities overweighted, hence lottery tickets AND insurance; the certainty effect), the fourfold pattern (risk-averse for likely gains and unlikely losses; risk-seeking for unlikely gains and likely losses), and framing effects (“90% uptime” vs “10% downtime” flip the choice).

Loss aversion is contested, not debunked. Gal & Rucker (2018), “The Loss of Loss Aversion,” argue it is far more context-dependent than the “universal 2x law” implies; gains can loom larger at small magnitudes (Harinck et al., 2007) and predicted pain of loss overstates the actual (Kermer et al., 2006). Real in many settings (especially higher-stakes, endowed goods) but not a context-free constant. Use it as a hypothesis to test for this customer, not a guaranteed lever.

4. Bounded rationality & satisficing (Simon) vs ecological rationality (Gigerenzer)

5. Mental accounting & present bias

6. Choice architecture & nudges (Thaler & Sunstein, 2008) and boosts (Hertwig)

7. Debiasing

You cannot will a bias away, but structured procedures help: consider-the-opposite (best-evidenced general debiaser, strong against anchoring/overconfidence), premortem (Gary Klein) (imagine the project has failed and explain why; prospective hindsight, cheap and high-yield), reference-class forecasting (Flyvbjerg / Kahneman’s “outside view”) (estimate from the distribution of comparable past cases; the fix for the planning fallacy), and checklists (force System 2 through a disciplined pass; only work with consistent adherence). Procedures and worked scenarios: references/debiasing-and-application.md.

Operator quick-map (bias -> tell -> move)

This table is a hypothesis generator, not a verdict. Treat the observed “tell” (what the customer said or did) as data, not a confirmed diagnosis. A tell suggests a candidate effect; confirm it against this specific person/context before acting (several effects are context-dependent). If the tell is ambiguous, gather one more observation or ask a clarifying question first. Never state the bias label to the customer or imply they are irrational; the label is your internal hypothesis, the “move” is what you do.

Situation / tell Candidate effect (verify) Operator move
First price/number sets the whole conversation Anchoring Set the anchor first; if anchored against, re-anchor with your own reference before negotiating
“We’ve already sunk 18 months into this design” Sunk-cost fallacy Reframe to the marginal decision from today; make past spend explicitly irrelevant
“Let’s just keep what we have / leave it as-is” Status-quo / default bias Make the better option the default; reduce switching friction; or set a decision deadline
Renewal framed only as new spend Reference dependence / framing Reframe against the reference point (cost of losing current capability, not net-new cost)
Team is 90% sure the timeline holds Overconfidence / planning fallacy Reference-class forecast + premortem; widen the interval
Customer fixates on the rare catastrophic risk Availability + probability weighting Provide base rates as natural frequencies (“3 in 1,000,” not “0.3%”) — a boost
Buyer stopped at the first “good enough” vendor Satisficing (bounded rationality) Don’t assume full comparison happened; be the easy, salient option that clears the bar
You catch yourself collecting only confirming evidence Confirmation bias Consider-the-opposite; assign a devil’s advocate
Post-incident “it was obviously going to fail” Hindsight bias In the postmortem, reconstruct what was knowable at the time (see postmortem-writing)
Signup/cancel flow has hidden friction Sludge Remove it; measure completion; opt-out only where it serves the user

Anti-patterns

Cross-references

Sources