thinking-cynefin
Cynefin Framework
Overview
The Cynefin framework, developed by Dave Snowden, classifies problems into domains based on the relationship between cause and effect. Different domains require fundamentally different approaches. Using the wrong approach for the domain leads to failure—agile doesn't fix truly complex problems, and detailed planning doesn't help in chaos.
Core Principle: The nature of the problem determines the nature of the solution. Match your approach to the domain.
When to Use
- Choosing the right methodology for a project
- Understanding why an approach isn't working
- Designing processes for different problem types
- Deciding how much to plan vs. experiment
- Understanding organizational challenges
- Incident response and crisis management
Decision flow:
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