General thinking tools · 0 connections

Map is not the territory

The map–territory relation

Any representation of a thing is not the thing itself — and a representation is useful only to the degree that its structure matches the structure of what it represents.

Explanation

Every time you act on a description, a model, a number, or a plan, you are acting on a representation — not on the thing the representation is about. The representation was made by filtering reality through a nervous system, a language, a set of instruments, or a set of assumptions. Something was left out. Something was simplified. The gap between the representation and the thing it represents is not a defect to be fixed; it is the nature of representation. That gap does not make representations useless. An equation that describes how a gas behaves under ordinary conditions is not exactly true for any real gas — yet engineers reach for it first, because its structure captures the relationships that matter across most conditions they will actually encounter. The equation works not because it duplicates reality but because it preserves the right shape of it. The question a representation demands is not "is this perfectly accurate?" but "does this preserve the structure I need, and are the parts it gets wrong important for what I am about to do?"

Watch

No video has yet earned its place here.

When it applies

The clearest trigger is when a model, a number, a category, or a plan is being treated as though it *is* the situation rather than a description of it — when the label settles the question, when the forecast closes the discussion, when the plan survives contact with the territory only because no one has checked. The second trigger is when you are deciding whether a representation is good enough to act on. "Good enough" is not a question about accuracy in the abstract. It is a question about which errors matter for this use. A representation that is wrong in ways that do not affect your decision is still load-bearing. A representation that is wrong in exactly the ways your decision turns on is not.

Where it stops

This lens does not help when the goal is to make a representation match the territory more exactly. A perfectly faithful representation would have to include a representation of itself, and that representation would need its own representation, without end. Perfect fidelity is not a reachable target — it is an incoherent one. The lens tells you that the gap exists and that you should check whether it matters; it does not give you a method for closing the gap. And adding more detail to a representation does not make it correct — it makes it more elaborate. Elaboration and correctness are not the same thing, and pursuing one does not produce the other. When the task is improving a representation's accuracy, you need a different tool.

The misuse

The most common misuse by someone who knows this concept is keeping only half of it. The half that travels well is "the representation is not reality." The half that gets dropped is "a representation is useful when its structure matches the structure of what it represents." Drop the second half and the concept becomes a reason to distrust any representation — a licence to dismiss a model, a forecast, or a plan on the grounds that it is not perfectly accurate, without asking whether its structure is sound enough for the job. The concept does not say representations are suspect. It says the gap between a representation and reality is always present, and that the right response is to check whether the gap matters — not to treat the gap as disqualifying.

A worked example

The ideal gas law — PV=RT — relates the pressure, volume, and temperature of a gas. No real gas obeys it exactly. At high pressures and low temperatures, molecules interact with each other and take up space, and the equation's predictions drift from what actually happens. Engineers reach for it first anyway. Its usefulness does not depend on its exactness. The structure of the equation encodes a physical picture of molecules moving and colliding, and that picture captures the relationships that matter across a wide range of ordinary conditions. Its known failure modes — high pressure, low temperature — point directly to where a more elaborate model is needed. A modeler who discarded the equation because it is wrong would lose the load-bearing approximation. One who treated it as exactly true would misread high-pressure behaviour. The concept operates in the gap between those two errors: the equation is wrong, its wrongness is understood, and it is useful precisely because the parts that are wrong do not matter for most of the work.

Push

Ask which parts of the representation are wrong in ways that matter for this specific use — not whether the representation is perfectly accurate.

Veto

Do not require a representation to be complete or exact before acting on it.

Connects to

Connections appear as the deck grows.

Go deeper

Mastery question

**Question:** A colleague dismisses a financial model by saying "it's just a model — it doesn't capture everything." You know the model leaves out several real-world factors. Is your colleague applying this concept correctly? **The answer:** Not quite. The concept does not say a model is suspect because it leaves things out — every model does. The right question is whether the things left out matter for the decision at hand. If the omitted factors are not important for this use, the model can still be load-bearing. Your colleague has kept the first half of the concept ("the representation is not reality") and dropped the second ("check whether the gap matters"). **The answer that misses it:** "Yes — if the model doesn't capture everything, it can't be trusted." **Why the difference matters:** Treating incompleteness as disqualifying would rule out every representation, because no representation is complete. The concept is a test of fit for purpose, not a general warrant for distrust. The question is always: wrong in which ways, and do those ways matter here?