Circle of Competence
4 min read
Core idea
The circle is the set of topics where your judgment is reliable
Warren Buffett popularized the phrase circle of competence to describe the set of subjects on which a person genuinely understands the underlying dynamics — not just the surface facts, but the second-order effects, the failure modes, the historical patterns, the things that look obvious to insiders and surprising to outsiders. Inside the circle, your intuition is a reliable signal. Outside it, your intuition is just confident guessing. The boundary matters more than the size.
Knowing where the boundary is matters more than how big the circle is
A small circle that you understand the edges of is far more valuable than a large circle whose edges you cannot see. Buffett's circle is famously narrow — he avoided technology investing for decades — but the precision of his self-knowledge is what let him compound capital for sixty years. The expensive failure is not lacking competence in some area; it is falsely believing you have competence you do not. Disasters in investing, medicine, governance, and engineering very often have the same shape: a smart person stepped confidently outside their circle without realizing they had crossed the line.
Why it matters
Confidence calibrated to actual competence is the asset
Everyone has some circle. The question is whether your felt confidence in any given domain matches your actual ability to predict outcomes in it. People who answer this well make fewer catastrophic errors, because they decline to play games they cannot win. People who answer it poorly take on risks they cannot evaluate, justify them with credentials from unrelated fields, and discover the mismatch only when the bill comes due. Self-knowledge is a moat.
The outside view is the antidote to imagined expertise
The fastest way to misjudge your own competence is to grade your own paper. Real circles are tested against the world — by track record, by feedback, by being demonstrably wrong in public sometimes. Imagined circles are tested only against your own confidence, which always passes. Anyone who has never been embarrassingly wrong in a domain probably does not have a real circle there yet; they have a comfortable-feeling map of unknown accuracy.
Key takeaways
Mental model
Practical application
-
Inventory your circles by topic. For any decision in front of you, ask: do I have a track record here? Have I been right and wrong publicly in this domain? Have I cycled through the failure modes enough to know what they feel like in advance? If the honest answer is no, you are not yet inside the circle.
-
Map the edges, not just the center. Write down what you don't know about a topic you think you understand. Beginners list their expertise; experts list their unknowns. If your "what I don't know" list is short, your circle is probably smaller than you think.
-
Grade against the world, not your self-image. Ask trusted people in your domain where they think your blind spots are. Their answer is the cheapest competence audit you can run.
-
Outside your circle, default to humility. Outside the circle, the moves are: (a) defer to someone whose circle covers it, (b) reason from first principles slowly, or (c) decline to act if the cost of error is large. The wrong move is to extrapolate from an adjacent circle as if it were the same domain.
-
Notice when others want you outside your circle. Sales conversations, expert advice, and meetings full of people you want to impress all reward the appearance of competence over actual competence. The pressure to overstate your circle is constant and often well-intentioned.
Example
A senior engineer hires a kitchen contractor
A staff-level software engineer is renovating her kitchen. She is excellent at evaluating distributed-systems trade-offs and at reading code. She is also used to being the smartest technical person in most rooms. When the contractor proposes a layout, she pushes back on the load-bearing wall placement and the electrical run, using analogies from system architecture. The contractor, polite but cornered, agrees to her plan.
Three months later the inspector flags two code violations, the layout has obstructed a key support, and the rework costs more than the original quote. The engineer is competent — extraordinarily so, in her field. The contractor is competent in his. The failure was not lack of intelligence; it was a confident extrapolation from one circle into another whose dynamics looked superficially similar (constraints, dependencies, optimization) but obeyed entirely different rules (building codes, structural physics, local inspector tolerances).
The cheaper version of this story is the one where the engineer says: "Walk me through why you laid it out this way. I can ask good questions, but I'm going to defer to your judgment on the structural and code parts." That single sentence is a circle-of-competence move worth several thousand dollars.
Related lessons
Related concepts
- Circle of Competencelinked concept
- Mental Modelslinked concept
- Self-Knowledgelinked concept
- Feedback Loopslinked concept