cognitive-bias-and-mindset-control

name	cognitive-bias-and-mindset-control
description	Surface the cognitive traps that corrupt a forecast's reasoning (as distinct from its data or math); use when a defensible-looking forecast may rest on biased judgment.
kind	skill
status	ready
provenance	{"principles":["P001","P008","P016","P017","P019","P020","P027","P033","P034","P041","P042","P045","P057"],"claims":["C00694","C00695","C00299","C00300","C01085","C01086","C00980","C00981","C01380","C01456","C00588","C00685"],"evidence":["E00088","E00089","E00021","E00022","E00215","E00216","E00159","E00160","E00369","E00430","E00055","E00085"],"source_anchors":["d88ef7714f29-c0008","3a2b4f822beb-c0007","e3c7c0b4e46f-c0009","e3c7c0b4e46f-c0003","5da0a790f5ae-c0002","5da0a790f5ae-c0006","d88ef7714f29-c0003","5da0a790f5ae-c0014","5da0a790f5ae-c0003","5da0a790f5ae-c0008","5da0a790f5ae-c0000","5da0a790f5ae-c0012"],"authored_from_digest":"0b7b85c0be3b5aacc5ba345128a154e346cf5bac6d604cd3d3c71fb693224912"}

Cognitive Bias and Mindset Control

Purpose

Surface and counter the cognitive traps that corrupt a forecast's reasoning — as distinct from its data, its model, or its arithmetic. A forecast can rest on a defensible base rate and a proper scoring rule and still be compromised for purely psychological reasons: a mind-set nobody thought to break, a lesson from history misdiagnosed as stupidity rather than complexity or sample bias, an illusion of validity mistaken for evidence, a hindsight or unpacking error left unmanaged, a recent win or loss anchoring the current call, a small sample over-trusted, or a counterfactual argument shaped more by commitment and dissonance reduction than by evidence. This skill locates those traps in a forecast's reasoning trail and prescribes the specific corrective for each, so the review addresses the thinking that produced the number, not only the number itself.

When to use

• The forecast's justification leans on a confident, coherent narrative rather than a base rate or a track record (P020).
• The reasoning invokes a historical analogy, a "lesson learned," or a recent success or failure to justify the current call, and it is unclear whether the lesson was actually earned (P001, P019, P027).
• Small anomalies are accumulating against a standing view, or a low-probability, high-consequence scenario has never been seriously worked through (P008).
• A claim rests on a handful of cases, or a counterfactual argument is doing heavy lifting in the reasoning (P057, P033, P041).
• The review is a post-mortem on a past forecast and needs to be run against the actual recorded prediction rather than anyone's memory of it (P042, P045).
• The reasoning needs to be checked against active open-mindedness and the four standing cognitive obstacles before it is trusted (P016, P017).

Procedure

Work through the reasoning trail in this order; not every step will find a flaw, but every step should be checked before the review is called complete.

1. Attribute poor learning from history to complexity and sample bias, not stupidity (P001). When a forecaster or decision-maker appears to have drawn a bad lesson from history, do not default to "they weren't smart enough." Look instead for the grounded causes: the underlying subject really is complex, the person only observed a small and skewed slice of past cases, the conditions under which they learned were poor (no clean feedback loop), or a settled view of the past is quietly steering the present read. A related blind spot: because people anchor on dramatic outcomes and have no explicit theory of what would count as "surprising," they systematically under-learn from non-events — the crisis that was quietly defused, the aggression that never came. This applies most when a confident forecast rests on a tidy account of past events, when planning stretches past a reliable horizon, or when a past outcome is being used to set expectations for a new case that only superficially resembles it (P001).

2. Break a fixed mind-set by thinking backwards (P008). When a mind-set has calcified around one reading of the situation, do not keep arguing forward from "will this happen." Flip the direction instead: assume the surprising, low-probability outcome has already occurred, then work backward to explain how it got there. That single move turns the question from whether into how, and it is the most useful lever exactly where mind-sets are most dangerous to leave unchallenged — the rare, high-consequence scenario nobody wants to take seriously (P008).

3. Practise active open-mindedness (P016). Check whether the forecaster holds their view as a hypothesis still open to disproof, or as a possession being defended. Active open-mindedness means giving disconfirming evidence and dissenting voices genuine weight, counting a revised opinion as a sign of rigor rather than a defeat, and deliberately seeking out sources that will not simply echo the standing view. The discriminating factor is self-critical habit, not raw intelligence — flag any account whose confidence far outruns its self-scrutiny (P016).

4. Anticipate the four cognitive obstacles (P017). Before accepting a forecast — or while building the review — check it against four standing obstacles: a pull toward the simplest available story, discomfort with ambiguity and dissonance that gets resolved by premature certainty, a need to see the world as more orderly than it is, and a shaky intuitive grasp of chance. For each, ask whether a deliberate corrective was built into the reasoning, or whether the obstacle was simply left to operate unchecked (P017).

5. Expose the illusion of validity (P020). Treat a forecaster's confidence, and the coherence of the story behind it, as a feeling produced by how easily the pieces fit together — not as a measure of how accurate the forecast will turn out to be. Coherent, confident impressions have coexisted with near-zero predictive accuracy, and the diagnostic tell is that the confidence typically survives even after the forecaster learns the account has no validity. When a review meets "I'm sure because it all fits," ask for the track record, not more narrative (P020).

Inputs

• The forecast's reasoning trail, not only its stated number — the narrative, analogy, or historical lesson used to justify it (P001, P008).
• Any precedent, "lesson learned," or recent success or failure the current recommendation is reacting to, reversing, or over-correcting from (P019, P027).
• The confidence or certainty language used, and whether it is backed by a track record or only by narrative coherence (P020).
• The sample or case base behind any empirical claim in the reasoning — how many cases, and how they were selected (P057).
• Any counterfactual claim in the reasoning, and who is making it (P033, P041).
• For a post-mortem: the original prediction exactly as recorded at the time, not as currently recalled, plus the actual outcome (P042, P045).

Output

Produce a findings list, highest-impact first. Each finding follows a fixed four-part shape:

• Flaw — name the specific cognitive trap and the principle it violates (cite Pxxx).
• Correction — the corrective action: think backwards from the outcome, seek out disconfirming evidence, ask for the track record instead of the narrative, check both the hindsight and the unpacking direction, ask whether the present case truly resembles the one invoked from history, compute rather than eyeball a sample's adequacy, or run the post-mortem against the recorded number.
• Residual uncertainty — what remains unresolved even after the correction (for example, the true base rate for this class of event, whether the invoked precedent really parallels the current case, or whether an improbable event simply occurred).
• Next step — a concrete action for the caller (for example, restate the prediction as a probability tied to a named reference class, pull the original recorded number before the debrief, or add a dissenting reviewer to the panel).

Never close a review with a bare narrative critique and no correction attached, and never let a single named flaw stand in for the full four-part finding — at minimum, produce one complete finding of this shape before returning control to the caller.

Anti-patterns to flag

• Treating a coherent, confident story as if it were evidence of predictive accuracy — confidence tracks narrative fit, not hit rate (P020).
• Explaining a bad historical lesson by "the person wasn't smart enough" instead of the case's complexity, a small or biased sample, poor learning conditions, or an unexamined view of the past (P001).
• Reversing a failed policy's tactics while keeping its goals, without checking whether the discarded alternative would have worked or whether this situation truly resembles the last one (P019).
• Excess caution after one costly outcome that forfeits a now-open opportunity, or a winning faction so entrenched by its own success that it cannot ask what happens if its optimistic assumptions fail (P027).
• Holding a mind-set unchanged while small anomalies accumulate against it, with no "think backwards" check ever run on the alternative (P008).
• Treating a change of mind as weakness, or avoiding sources likely to disconfirm the standing view (P016).
• Accepting a forecast without checking it against the four standing obstacles — simplicity- seeking, ambiguity aversion, a need for orderliness, and a weak grasp of chance (P017).
• Drawing a firm conclusion from a small number of cases, or setting a sample size by feel rather than by computing the risk of being wrong (P057).
• A counterfactual argument that tracks the arguer's ideology or dislike of an actor more than the evidence, especially once the arguer is visibly committed to the generalization it would undercut (P033, P041).
• Running a post-mortem from unaided memory of "what I predicted" instead of the verbatim recorded number, or accepting "I was almost right" or "it was just off on timing" as if it vindicated the original call (P042, P045).
• Fixing only the hindsight error (treating the past as if it had to happen) while leaving the mirror-image unpacking error (treating every named future branch as more likely once described) unexamined, or vice versa (P034).

References

• ../../references/calibration-forecasting-principles-index.md — full statements, applies-when contexts, and the claim/evidence/source-anchor trace for every principle cited above.

Provenance

This skill body derives solely from P001, P008, P016, P017, P019, P020, P027, P033, P034, P041, P042, P045, P057; see the frontmatter provenance block above for the associated claims, evidence records, and source anchors.