How I Know What Is True

The Map Is Not the Territory

Also called: Map-territory distinction

Personal interest
Philosophical question
Working interpretation

Words and diagrams help us find our way, but they can quietly take the place of what they describe. I am interested in noticing the moment an idea hardens into an assumption I no longer question.

Where have I started defending the map instead of looking at what it describes?

Why it attracts me

Most of my tools are maps of one kind or another: diagrams, dashboards, models, graphs. What interests me is the quiet moment when a map stops being a guide and starts being treated as the thing itself.

The idea

Every description chooses what to show. A word groups many different things under one label. A chart shows what was measured and hides the rest. That choice is what makes maps useful, and it is also how they mislead. The answer is not to give up maps. It is to remember that someone drew them, for a purpose.

An example

The essay Network Science for Engineers contrasts two ways of looking at the same factory work. One is a list of tasks sorted by how many dependencies each has. The other is a graph that shows how the tasks connect. The essay notes that a task with few links can still be critical if it bridges two large groups of work, and that sorting the list "can miss the actual vulnerability." Same factory, two maps, different blind spots.

Where it connects

This is a close cousin of Models Are Not Reality. It also links to How the Mind Builds What We See: perception is itself a kind of map the brain builds, which is part of why experience and the world are not the same thing. And this whole atlas is a map. Its clusters show how I chose to draw my ideas, not the shape of my mind.

Questions I'm still exploring

Which labels I use for myself have stopped being useful descriptions?
How can a map show its own blind spots?
Is anything I experience not already a kind of map?

Sources and further reading

Alfred Korzybski, Science and Sanity (1933) — Source of the phrase "a map is not the territory."

Working interpretation: drafted from my notes and interests for review. It is not a direct quotation, and I may still change it.

In short

A map is useful because it leaves things out. The trouble starts when we forget it is a map and treat the label, chart or category as if it were the thing itself. The scholar Alfred Korzybski put it as "a map is not the territory." Words, dashboard numbers, job titles and diagrams all work this way: they point at something real without being it.

Why this matters to me

Much of what I build is a map of some kind: flow diagrams, graphs, models, and now this map of my own ideas. Each one helps me see something, and each one can harden into a picture I defend instead of check. I want to keep noticing when a label has replaced a question. That applies to engineering data, and just as much to the categories I use for myself and for other people.

Connections

How the Mind Builds What We SeeAnalogy

The brain builds perception, a bit like drawing a map, which is a reminder that what I experience is not the same as the world it stands for. Perception shows that the mind's inner models should not be mistaken for reality itself. What I experience is a useful map of the world, not the world directly.

Reasoning From the Ground UpPart of

Reasoning from basics means looking past labels and diagrams to what they describe, and noticing when a description has hardened into an assumption.