thinking-circle-of-competence
Circle of Competence
Overview
The Circle of Competence, articulated by Warren Buffett and Charlie Munger, emphasizes knowing the boundaries of your genuine expertise. The key insight isn't about having a large circle—it's about knowing precisely where your circle ends. Operating within your circle leads to better decisions; operating outside it without recognizing it leads to costly mistakes.
Core Principle: "Know what you don't know. The boundaries of your circle are more important than its size." — Warren Buffett
When to Use
- Evaluating new opportunities or projects
- Making decisions in unfamiliar domains
- Assessing whether to delegate or learn
- Investment or resource allocation decisions
- Taking on new responsibilities
- Advising others on topics
- Hiring or team composition decisions
Decision flow:
Decision to make? → yes → Inside your circle? → yes → Proceed with confidence
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