// Apply Kahneman's Dual-Process Theory to recognize when to trust intuition vs engage deliberate analysis. Use for high-stakes decisions, error-prone contexts, or when balancing speed vs accuracy.
Recognize Senge's Systems Archetypes to diagnose recurring organizational and technical problems, identify why fixes keep failing, and design interventions that address root structure.
Update beliefs systematically based on new evidence using probabilistic reasoning. Use when estimating probabilities, learning from data, or making decisions under uncertainty.
Apply Herbert Simon's Bounded Rationality and satisficing to make good-enough decisions under real-world constraints. Use for design decisions under time pressure, recognizing cognitive limits, and setting appropriate stopping criteria.
Know the boundaries of your expertise and operate within them. Use when evaluating opportunities, making decisions outside your domain, or assessing when to defer to experts.
Classify problems by complexity domain (clear, complicated, complex, chaotic) and match approach to domain. Use for choosing methodologies, problem framing, and process design.
Systematic checklist to identify and counteract cognitive biases in decision-making. Use before major decisions, when evaluating recommendations, or when stakes are high.
| name | thinking-dual-process |
| description | Apply Kahneman's Dual-Process Theory to recognize when to trust intuition vs engage deliberate analysis. Use for high-stakes decisions, error-prone contexts, or when balancing speed vs accuracy. |
Based on Daniel Kahneman's research (popularized in "Thinking, Fast and Slow"), Dual-Process Theory describes two distinct modes of thought: System 1 (fast, intuitive, automatic) and System 2 (slow, deliberate, analytical). Understanding when each system is active—and when each is appropriate—helps you avoid cognitive errors and make better decisions.
Core Principle: Know which system is driving your thinking. Engage System 2 for high-stakes decisions; trust System 1 for routine tasks and expert domains.
Decision flow:
Making a decision? → High stakes? → yes → Unfamiliar domain? → yes → ENGAGE SYSTEM 2
↘ no → System 1 may suffice
↘ no → Time pressure? → yes → System 1 appropriate
↘ no → Choose based on complexity
| Characteristic | Description |
|---|---|
| Speed | Instant, automatic |
| Effort | Effortless, no strain |
| Control | Involuntary, always on |
| Mode | Intuitive, associative |
| Emotion | Emotionally charged |
| Basis | Pattern recognition, heuristics |
System 1 excels at:
System 1 fails at:
| Characteristic | Description |
|---|---|
| Speed | Slow, sequential |
| Effort | Effortful, depleting |
| Control | Deliberate, voluntary |
| Mode | Analytical, rule-following |
| Emotion | Can override emotions |
| Basis | Logic, computation, rules |
System 2 excels at:
System 2 fails at:
Which system is currently driving your thinking?
System 1 indicators:
System 2 indicators:
Example: "Should we approve this vendor contract?"
Gut says "yes" immediately → System 1 active
Pause: Is this appropriate for this decision?
Is the active system appropriate for this context?
Trust System 1 when:
Engage System 2 when:
If System 1 is active but System 2 is appropriate:
1. PAUSE - Interrupt automatic response
2. ARTICULATE - State the decision explicitly
3. ANALYZE - Apply structured thinking
4. CHECK - Look for bias indicators
5. DECIDE - Make deliberate choice
Override triggers (red flags):
Match your process to the system:
| System | Process |
|---|---|
| System 1 (validated) | Trust intuition, act quickly, monitor outcomes |
| System 2 (engaged) | Use checklists, seek outside view, document reasoning |
System 1 replaces hard questions with easier ones:
Hard: "How much should I pay for this stock?"
Substituted: "How much do I like this company?"
Hard: "Is this candidate qualified?"
Substituted: "Does this candidate seem likeable?"
| Heuristic | What It Does | When It Fails |
|---|---|---|
| Availability | Judges by ease of recall | Vivid events seem more common |
| Representativeness | Matches to stereotypes | Ignores base rates |
| Anchoring | Starts from given number | Arbitrary anchors still influence |
| Affect | Decides by feeling | Emotions override data |
| Confirmation | Seeks supporting evidence | Misses contradicting evidence |
System 1 builds the best story from available information:
Given: "John is tall and muscular"
System 1 concludes: "John is probably athletic"
Missing: John's actual athletic ability, base rates, context
System 1 doesn't flag missing information—it works with what's available.
Feels: Familiar, true, good, effortless Risks:
Induced by:
Feels: Unfamiliar, requiring effort, suspicious Benefits:
Induced by:
Tactical tip: For important decisions, deliberately induce mild cognitive strain (different format, pause before answering) to engage System 2.
System 1 mode: "This looks fine" (pattern matches familiar code)
Engage System 2:
- Is this a high-risk change?
- Am I the right reviewer for this domain?
- Have I actually traced the logic?
- What edge cases might I miss?
System 1 mode: "Great interview, strong hire" (likeability heuristic)
Engage System 2:
- Structured scorecard vs overall impression
- Compare to job requirements, not to other candidates
- Check for halo effect from one strong answer
- Seek disconfirming information
System 1 mode: "Let's use [familiar technology]" (availability)
Engage System 2:
- Explicit requirements analysis
- Evaluate alternatives against criteria
- Consider long-term implications
- Document reasoning
System 1 mode: "It's probably X" (first hypothesis feels right)
Engage System 2:
- List all possible causes
- Assign probabilities (Bayesian)
- Test systematically, not just hunches
- Consider unlikely explanations
System 1 is the source of most cognitive biases. The debiasing checklist is essentially a System 2 override protocol:
Automatic response → Pause → Apply debiasing checklist → Override if needed
System 1 ignores base rates; System 2 applies them:
System 1: "Positive test result = probably have condition"
System 2: Apply Bayes' Theorem with actual base rates
System 1 reasons by analogy; System 2 enables first principles:
System 1: "Competitors do X, so we should too"
System 2: "What are the fundamental requirements? Build from there"
System 1 is optimistic; pre-mortem forces System 2 pessimism:
System 1: "This plan will work" (overconfidence)
System 2: "Imagine it failed. Why?" (deliberate analysis)
Balance speed (System 1) with accuracy (System 2) based on context:
Incident response: System 1 pattern matching for speed
Post-incident: System 2 analysis for root cause
Not all intuition is suspect. Expert intuition can be trusted when:
Valid expert intuition:
- Chess grandmasters recognizing positions
- Firefighters sensing danger
- Experienced nurses detecting deterioration
Suspect expert intuition:
- Stock pickers predicting markets
- Political pundits forecasting elections
- Interviewers predicting job performance
Ask: "Has this person had opportunities to learn the valid patterns through repeated, well-calibrated feedback?"
"The confidence people have in their beliefs is not a measure of the quality of evidence but of the coherence of the story the mind has managed to construct."
System 1 builds compelling stories from limited information and feels very confident doing so. That confidence is often unwarranted. Engage System 2 when the stakes matter.