# The map is not the territory

26 September 2026 · Essay · 10 min read

By [Ahsan Fazal](https://axiomatic.digital/en/about#ahsan), Founder and CEO

A care organisation’s knowledge is four maps of one territory, the moment of care. It stays true as long as the maps are read at that moment and redrawn by it. Inora keeps both directions running and never reads the territory itself.

## 22:40

A ward in a nursing home, the evening shift. A new aid arrived this afternoon. The supplier explained it to the staff on duty at the time. The evening nurse was not there, and at 22:40 wants to know how to clean it before the night begins.

The nurse asks Inora. It is in no source: not in the organisation’s work agreements, not in the region’s agreements, not in a national guideline. The team has nothing on paper about it either, and the colleague who was there for the explanation has gone home.

What happens next decides whether the organisation learns. If the software guesses, the answer sounds sure and no one knows whether it is right. If the question stays with the nurse, a colleague asks the same thing tomorrow evening and finds nothing either.

Today we set down how we see a care organisation’s knowledge, in a model with a figure. It is called Map and Territory. This is the long version. It begins at 22:40, and it ends there too.

## A map is not the territory

In 1931 Alfred Korzybski used the phrase that has stayed with us ever since: the map is not the territory. Two years later he wrote out the whole thought, in *Science and Sanity* (1933, p. 58): “A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness.”

A map is useful because it is not the territory. It leaves things out, and what it keeps has the territory’s shape. Jorge Luis Borges made a short story of it in 1946, “Del rigor en la ciencia”. The cartographers of an empire drew a map as large as the empire, point for point. The generations after them found it useless and left it to the sun and the winters. A map at 1:1 is no longer a map.

That has a consequence for every care organisation. There is no single map of everything, and anyone who tries to draw one draws Borges’s map. An organisation needs several maps, each at its own scale, each leaving out what another knows.

In care, the territory is the moment of care itself: this shift, this client, what no protocol foresaw. Every map is a map of it. None of them is it.

## Four maps

The model fits in six words. Four maps. One territory. One line.

**The national map** has the coarsest scale: professional standards, national guidelines, the law. It changes over years and applies everywhere, and for exactly that reason it knows nothing of this ward at 03:10. It counts where the organisation designates it and its publisher allows it.

**The regional map** holds what the organisations of a region agree together: transmural agreements, the escalation agreement with the treatment service, the lab guide, the regional toolbox. It knows the space between organisations, where care breaks down most often, and not how any one organisation works inside. The network owns it, and each organisation adopts it source by source.

**The organisation’s map** is what the organisation says it does: its protocols, work agreements, procedures and quality handbook, its report formats and the practices its teams recorded. Its legend is its direction: its goals, vision and methods. This is the leading map. What arrived on the ward this afternoon is not on it yet.

**The team’s map** is how this team really does the work: the order that works on this ward at night, the colleague everyone asks, the workaround nobody wrote down. It is the finest map and the nearest to the ground, and most of it is not on paper. Michael Polanyi gave it its sentence in 1966, in *The Tacit Dimension* (p. 4): “We can know more than we can tell.” This map does not travel. A colleague who knows it takes it home when going off duty.

In the figure the four maps lie one above the other, each exactly over the same ground and each carrying the terrain’s contours at its own scale. The terrain’s finest ripple is on no map. Only the territory is at 1:1.

FIG 1 · Model

Map and Territory

![Isometric drawing of the Map and Territory model: four glass maps above a block of terrain. From the top, the national map, the regional map, the organisation’s map and the team’s map, each carrying the terrain’s contours at its own, coarser scale. Below them a dashed line at the height of the professional’s head, and at the bottom the territory itself, the moment of care. Warm rises: what is lived redraws the map. Cool descends: the map is read, in the moment itself. Below the dashed line the professional decides.](https://axiomatic.digital/_astro/en-narrow.54xUIwI4.webp)

Four maps. One territory. One line. A care organisation’s knowledge as four maps of one territory, the moment of care.

## The organisation decides which map leads

Which map applies? The organisation decides, not Inora and not us, and it has usually written it down already in its quality handbook. Inora takes that order as it stands. A reference from one map to another never changes which one leads.

Take 08:10, morning care. A client wants to learn to put on her compression stockings herself. The team has nothing on paper about it. The organisation’s work agreement does, and it points to the national protocol and the regional toolbox. Because the organisation chose those three, the answer comes from those three maps, and each part is marked: one tap shows which map it comes from, with source, layer, version and passage. Where two of its sources disagree, the answer follows the one it has given precedence to and says in one sentence that the other differs. A source from outside the organisation never reaches the care worker. Every task gets from each map only what it needs, at that map’s own grain.

A general model has a map too. It is a map of everything it has ever read, and of no ground in particular. Where your organisation’s maps are silent, it fills in from what it read elsewhere, and it sounds just as sure when it is wrong.

Karl E. Weick tells, in *Sensemaking in Organizations* (1995), of a unit of soldiers lost in the snow in the Alps. One of them found a map in his pocket. They waited out the storm and found their way back with it. When their lieutenant looked at the map, it turned out to be a map of the Pyrenees. Weick draws the lesson that people who are lost get further with a map, whichever map, because a map gets them moving.

For soldiers in the snow, that is true. At 22:40 on a ward, it is exactly the danger. A fluent answer from a general model is the map of the Pyrenees: confident, and about other mountains. It gets a nurse moving, just not towards their own organisation’s work agreement. That is why in Inora the map that leads is the one the organisation chose to lead, and every answer marks which map each part comes from.

## Two directions

Knowledge in a care organisation runs two ways. Downwards, the map is read at the moment itself. Upwards, the map is drawn by what the work writes. That is slower, over a shift, and it takes three forms.

**The report.** At 14:30, at the end of the early shift, a senior care assistant writes a report in SOAP. Their own words go under the organisation’s headings. No fact they did not give is added; a conclusion a care worker would draw from their notes is set beside them, marked as inferred. A heading their notes leave empty stays open and comes back to them as what the protocol still asks for.

**The practice.** At 10:00, at the team meeting, the subject is how this team does the handover. That route was written down nowhere. It is drawn out of recent work, the quality adviser approves it, and it goes onto the organisation’s map with the team as its owner. How your best people do it becomes how everyone does it.

**The gap.** At 22:40 someone asks something that is on no map. I will come back to it.

Care now writes more than it looks up. Since June 2026 writing has been the largest use of Inora: a report, a handover, a letter, in the care worker’s own words. In September 2026 it was 52% of conversations. Looking something up was 39% over the year. Most of what moves in Inora moves up.

Gregory Bateson wrote in 1970, in “Form, Substance and Difference”: “What gets onto the map, in fact, is difference.” What rises is difference. A report is the difference a shift made. A practice is the difference between how a team works and what the handbook says. A gap is the difference between the map and the moment. A map that does not receive that difference drifts away from the ground. Only what rises keeps it true.

That is why Inora is where a care organisation’s knowledge is used, and also where it is made.

## The line

Inora reads maps, never the territory. It never looks at a client itself. The territory reaches Inora only through what the care worker tells it and what the record holds about this client.

Inora answers a question about the map from the nearest map that covers it, with the passage one tap away: what our protocol says, whom we call, what we record, how we do it here. For a question about one client, it puts that map beside the care worker and flags what is missing: what the agreement on a missed dose says, which escalation criteria apply and whom to call, which observations the MEWS or the Braden asks for. Each of the organisation’s sources is marked. Inora never suggests what might be wrong with a client and reads no photo of skin or a wound: only the person standing in the territory sees that.

The decision stays with the care worker.

In short: knowing is not yet choosing. The map gives the care worker the ground. The decision is theirs. In the figure this is geometry: no flow ends in the territory, and every flow starts or stops on the dashed line, at the height of their head.

## What it asks of an organisation

The model asks four things of an organisation.

**An owner for every map.** A source without an owner is a map no one redraws. Every document has one; the regional map has the network, the national map its publishers, and a team’s practice the team itself. That is why every implementation of ours starts with the quality handbook, with the quality adviser: who owns each document, which version applies, what has expired.

**A list that gets worked through.** Every topic without an answer, every contradiction between sources and every expired document lands as a task on the list of the person who owns that area of knowledge, without the question and without who asked it. A list no one opens is a second handbook no one reads.

**Direction as the legend.** What the board wants care to be decides how an answer is ordered and worded. Never what a source says.

**Every level in the same picture.** The care assistant who needs the nearest map at 03:10. The team leader who sees which topics their team asked about and which stayed open, in aggregate, never who asked. The quality adviser who works the list. The board, which sees in the monthly report which gaps have closed, summed across all teams. The same maps over the same ground, each seen from a different height.

## Back to 22:40

The nurse does not get a guess. Inora says the answer is not in the sources, where it looked and who owns the subject. They decide what to do tonight.

The topic goes to the owner of the organisation’s map, without the nurse’s question and without their name. The owner gets the answer from someone who knows it, the colleague who was there for the explanation or the supplier, and puts it in the work agreement. The map is redrawn and its version goes up by one. The owner writes a test question for Inora’s next release, and the monthly report shows the gap closed.

The next evening another nurse asks the same thing. They get the answer from their own organisation’s work agreement, with the passage one tap away.

That is what knowledge is, in a care organisation. Not a stock in a handbook, and not a talent in a few heads, but four maps read at the moment and redrawn by it. The map is not the territory. But the territory can draw the map, if someone takes the question at 22:40 seriously.

*Ahsan Fazal, managing director, 26 September 2026*

## Postscript, 2 November 2026

Inora is not a medical device. Inora supports triage: the professional triages, scores and decides. Inora puts the organisation’s own protocol beside the professional, flags what is missing and records the source and version of every answer; it does not diagnose or decide on treatment. Its intended use keeps it outside the medical device rules ([The professional decides](https://axiomatic.digital/en/trust#medical-devices)).

## Sources

- Alfred Korzybski, *Science and Sanity* (1933), p. 58.
- Jorge Luis Borges, “Del rigor en la ciencia” (1946).
- Michael Polanyi, *The Tacit Dimension* (1966), p. 4.
- Gregory Bateson, “Form, Substance and Difference” (1970), in *Steps to an Ecology of Mind* (1972).
- Karl E. Weick, *Sensemaking in Organizations* (1995).

## Do you work in care and use Inora?

Sign-in and help go through your own organisation: your team’s project lead and ambassadors can help you.

## Read on

- [The gap is not the model. It is the knowledge.](https://axiomatic.digital/en/updates/the-gap-is-not-the-model.md): The knowledge care runs on lives in the protocols and in the heads of the few people in every team who quietly do the work better. A general model does not bring the two together, not even with your documents added. A knowledge system does.
- [A question without an answer is work](https://axiomatic.digital/en/updates/a-question-without-an-answer-is-work.md): When the sources do not cover a question, a general model guesses. Inora says so, and the topic becomes a task for the owner of that knowledge, without the question and without the name of the person who asked. Then the owner writes a test question for the next version. That loop makes Inora better, not the model.
- [One system, three products](https://axiomatic.digital/en/updates/one-system-three-products.md): Three places got the same Inora and made three products of it: a handbook, a writing assistant and the go-to source for evenings and weekends. What that says about a knowledge system, and why we keep building one.
