Map ≠ Territory

Say this

What's the real world telling me — not the story I built?

Do this now 3 min

Write the plan, model, or assumption you're relying on. List two things it simplifies or ignores. Ask: when was this last tested against reality?

Use when

You're making a decision based on reports, forecasts, models, or opinions that feel neat and certain.

Avoid when

You're already testing in the real world and the feedback loop is live.

Why it works

Every model is a simplification, and every simplification hides risk — naming what's missing keeps you flexible when facts shift.

Every plan, model, forecast, and spreadsheet is a simplification. That’s what makes them useful — and dangerous. The danger is cognitive ease: a polished plan feels true because it’s fluent and coherent, and your brain mistakes that fluency for accuracy. The more confident a model makes you feel, the more important it is to ask what it leaves out. All knowledge is abstraction. The gap between the map and the territory is where surprises live, and surprises are where plans die.

Go deeper · 8 min read

Map vs Territory: Why Polished Plans Feel True and Why That's Dangerous

A polished plan feels true because it's coherent. But coherence is a property of the map, not the territory — and the gap between them is where every surprise, failure, and 'nobody saw it coming' moment lives.