Dual-System Thinking (System 1 / System 2)

Activate when: a decision feels obvious but the stakes are high; someone says 'I just trust my gut' on a consequential call; a team is converging fast without pushback; you're tired or pressured and still need to decide; you're in an unfamiliar domain moving on instinct. Do NOT activate when: the decision is genuinely routine and low-stakes; you have well-trained calibrated expert intuition in that exact domain and need to act fast.

Overview

Two parallel modes: System 1 — fast, automatic, effortless (pattern recognition, gut feel). System 2 — slow, deliberate, effortful (analysis, computation, critical evaluation). System 1 runs ~95% of decisions by default; System 2 engages only when recruited. Most cognitive biases are System 1 shortcuts misapplied where System 2 should have intervened.

Composes with metacognition, every cognitive-bias skill (anchoring, confirmation-bias, availability-heuristic, etc.), deep-work, and wu-wei.

When to Use

• Decision feels obvious and is high-stakes; unfamiliar domain + fast intuition; time pressure on consequential matter; team converging without stress-test; depleted (tired/hungry/pressured)
• Designing a process or interface that depends on user attention

Not when: routine low-stakes decisions; calibrated expert System 1 in this exact domain; emergency requiring speed.

Coaching Novices (Adaptive Front Door)

• Engine mode: user has a concrete decision → run The Process directly.
• Coach mode: user is unfamiliar → 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: when a high-stakes decision feels obvious, that obviousness is a warning — System 1 is firing and may need System 2 to check it.
2. Check fit: routine low-stakes decisions are fine for System 1. This framework is for consequential, novel, or statistically-loaded decisions.
3. Elicit the specific decision: what's being decided? Does it feel obvious? Are you tired / pressured / in your area of trained expertise?

[WAIT — do not advance until user responds]

4. Work through: what's the System 1 answer? what's the System 2 check? what bias might be active? what procedure forces System 2 engagement?

[WAIT — do not advance until user responds]

5. Close: name the system used and the procedure applied.

[WAIT — do not advance until user responds]

The Process

Step 1 — Identify decision + initial answer: note what comes to mind quickly, your confidence, and time-to-answer.

Step 2 — Classify system: quick + automatic + confident + no felt effort = System 1; slow + deliberate + uncertain + felt effort = System 2.

Step 3 — Recruit decision:

Stakes	Familiarity	Recruit System 2?
Low	High	No
Low	Low	Optional
High	High	Yes (verification needed)
High	Low	Mandatory

Step 4 — Recruit via procedure: write down the question; list 3 alternatives; name the active bias; apply a checklist; consult base rates; run a premortem; take 24h if possible.

Step 5 — Compare outputs: if S1 and S2 agree → high confidence. If they diverge → S2 wins for novel/high-stakes; in calibrated expert domains, S1 may be right. Document the reason.

Step 6 — Calibrate: log decisions + outcomes by domain. High-calibration domains: trust S1 more. Low-calibration: always recruit S2.

Output Template

text

Decision: | Initial answer: | Time to arrive: | Confidence:
System in operation: S1 / S2 / mixed
Stakes: H/L | Familiarity: H/L | Recruit S2: Y/N
Procedure used: | S2 outputs:
S1 said: | S2 said: | Agree/disagree: | Final answer + reason:
Calibration log — Domain: | System used: | Outcome (when known):

→ Method in Action: Kahneman 2011 + 40 Years of Tversky-Kahneman Research

Pack: Key Domain Patterns

Domain	S1 role	S2 role	Common error
Hiring	First impression	Structured rubric; work-sample	Halo effect dominates
Investing	Pattern recognition	Base rates; bear-case	"Good feeling" in novel domain
Medical diagnosis	Quick pattern-match	Differential; base rates	Anchoring on first impression
Strategic decisions	Founder intuition	Premortem; market analysis	Confident S1 without calibration

Applying It Well

"Obvious" is a warning, not a confirmation — treat it as a hypothesis. Structural System 2 recruitment (checklists, premortems, decision journals) beats willpower. Trained System 1 in a calibrated domain is valuable; outside that domain, it's dangerous.

→ Primary sources: references/sources.md

Common Rationalizations

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

Fake move	Reality
[D] "I trust my gut"	Sometimes warranted (calibrated domain). Often a defense against System 2 discipline. Check the track record.
[D] "It's obvious; we don't need to overthink"	"Obvious" is System 1 output. The check is cheap; the cost of wrong is high.
[D] "We have to decide fast"	Often speed pressure is exaggerated. Most "urgent" decisions absorb a 1-hour structured pause.
[D] "I'm an expert; my intuition is reliable"	Expertise is domain-specific. Rapid, accurate, repeated feedback in this exact domain?
[D] "Cognitive biases don't apply to me; I know about them"	Bias-blind-spot effect: knowing reduces biases weakly. Structural procedure is the corrective.
[D] "The team agrees; we don't need to second-guess"	Team consensus is often System 1 cascade. Premortems are the System 2 counter.
→ Add [O] entries here after each real use — paste the actual failure pattern	What went wrong and why

Red Flags

High-stakes decision feels obvious and you're not checking it · tired/pressured making consequential decisions · novel domain + fast intuition · team converging without pushback · "I just know" is your justification · decision in <30 seconds on meaningful stakes

Verification

• System in operation diagnosed (S1 / S2 / mixed)
• Stakes × familiarity matrix applied
• If recruitment needed, structured procedure used
• S1 and S2 outputs compared; divergence justified
• Active cognitive biases listed
• Decision logged for calibration

---

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.