thinking-dual-process
Dual-Process Thinking
Overview
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.
When to Use
- Making decisions with significant consequences
- Recognizing when intuition may mislead
- Balancing speed vs accuracy tradeoffs
- Reviewing work for cognitive errors
- Teaching or coaching decision-making
- When "something feels off" but you can't articulate why
- Before trusting a gut feeling on important matters
Decision flow:
Making a decision? → High stakes? → yes → Unfamiliar domain? → yes → ENGAGE SYSTEM 2
More from tjboudreaux/cc-thinking-skills
thinking-scientific-method
Hypothesis → Prediction → Test → Revise with explicit falsification. Use for debugging, feature experimentation, performance investigation, and A/B testing design.
29thinking-model-router
Route to the right mental model based on your domain and problem type. The single entry point for all thinking skills.
29thinking-socratic
Systematic questioning framework to deepen understanding, challenge assumptions, and uncover hidden beliefs. Use for requirements gathering, debugging, coaching, and critical analysis.
29thinking-inversion
Approach problems backward by identifying paths to failure, then systematically avoiding them. Use for risk identification, planning, and avoiding obvious mistakes.
28thinking-probabilistic
Express confidence in ranges, update predictions with new information, and track calibration over time. Use for project estimation, risk assessment, and decision making under uncertainty.
27thinking-red-team
Deliberately attack your own plans, systems, and assumptions to find weaknesses before adversaries or reality does. Use for security review, architecture validation, plan stress-testing, and pre-launch preparation.
27