Staying Grounded

Part 7 · The Practitioner’s Compass

The book closes where it began. The opening argument was that the frameworks are a map, and the map is not the territory. The territory is the organisation in front of you, the people in the room, and the problem that needs solving today. Everything between that opening and this closing — the frameworks, the concepts, the diagrams, the language, the practitioner arguments — was offered as map-reading instruction. This final chapter is about the discipline that all of it depends on: using the frameworks without being used by them, and staying connected to the reality the maps describe.

It is the discipline of staying grounded, and it is the hardest one to keep, because the frameworks exert a pull toward themselves that is easy to mistake for rigour.

The Pull of the Map

There is a characteristic failure that befalls people who learn the frameworks well. They begin to mistake the map for the territory — to believe that because they have modelled something, they understand it; that because the diagram is complete, the work is done; that because the process was followed, the decision is sound. The frameworks, learned thoroughly, exert a gravitational pull toward themselves, and the pull is seductive precisely because it feels like rigour.

The pull shows up as ceremony. The ADM run in full because the framework says so, regardless of whether each phase is warranted. The capability map elaborated to a level of detail no decision requires. The ArchiMate model maintained for its own sake. The governance process performed because process is what governance does. Each of these feels like good practice; each is the map substituting itself for the territory, the architect serving the framework rather than the organisation.

The deeper version of the pull is identity. An architect who has invested years in mastering the frameworks comes to value being right about the frameworks — being the person who knows the correct ADM phase, the proper ArchiMate notation, the canonical definition — and this is a subtle betrayal of the job, because the job was never to be right about the frameworks. It was to help the organisation make better decisions. The frameworks are instruments toward that end, and an architect who serves the instruments has forgotten the end.

How to Use Frameworks Without Being Used by Them

Staying grounded is the practice of keeping the frameworks in their proper place — as instruments, used selectively, in service of the territory. A few disciplines sustain it.

Always ask what the framework is for, here, now. Before running an ADM phase, modelling a capability, or drawing an ArchiMate view, ask what decision it will improve. If the answer is “it’s what the framework says to do”, that is not an answer — it is the pull of the map. The framework’s activities are warranted when they improve a decision and ceremonial when they do not, and the discipline is to apply them only when they do.

Keep the territory in view. The frameworks describe; the organisation exists. When the model and the reality disagree, the reality wins, and the model is wrong — not the other way around. The architect who, told that the live system behaves differently from the diagram, defends the diagram has been captured by the map. The grounded architect updates the diagram and is grateful for the correction, because the diagram’s only value is its fidelity to the territory.

Stay close to delivery. The surest antidote to the pull of the map is regular contact with the people building things and the reality they are building in. The enterprise architect who never leaves the strategy floor loses touch with whether the maps still describe anything real. Staying grounded means descending regularly to where the work happens — the altitude discipline of Chapter 49, applied to oneself.

Prefer the useful to the complete. A framework’s instinct is toward completeness — every cell modelled, every phase run, every artefact produced. The territory’s demand is for usefulness — the specific description that improves the specific decision. When completeness and usefulness conflict, usefulness wins, and the courage to leave the model incomplete because completing it would serve nothing is a mark of the grounded architect.

Keeping Delivery Instincts Alive

For readers who come to architecture from delivery — from development, infrastructure, operations, project work — there is a specific version of this discipline: keeping the delivery instincts alive after acquiring the architectural vocabulary.

The delivery instincts are precious and easily lost. The instinct that a plan must survive contact with reality. The instinct that the people doing the work know things the diagram does not. The instinct for what is actually hard versus what merely looks hard on a slide. The instinct to distrust a clean abstraction that has not been tested against a messy case. These instincts are exactly what the frameworks, learned uncritically, can erode — replacing the delivery person’s healthy scepticism with the architect’s faith in the model.

The grounded architect keeps both: the architectural vocabulary that lets them see the whole, and the delivery instinct that keeps them honest about whether the whole they see is real. The combination is more valuable than either alone, and it is the combination this book has tried to cultivate — which is why it grounded every concept in Meridian’s messy specifics rather than presenting the frameworks as clean abstractions. The delivery instinct is what reads a beautiful roadmap and asks “but what happens when the dependency slips?” — and that question is worth more than the roadmap.

Meridian: Three Years In

Meridian’s EA, three years into the work, reflects on what she kept and what she discarded — and the reflection is the book’s closing argument in a single life.

What she kept: the frameworks as instruments. She still uses the capability map, because it makes the estate visible and improves investment decisions. She still uses the ADM’s logic — vision, baseline, target, gap, roadmap — because it is a sound sequence of thinking. She still uses ArchiMate when a vertical trace will help a stakeholder see a dependency. She kept the parts of the frameworks that earned their place by improving decisions.

What she discarded: the ceremony. She does not run the full ADM as a ritual; she runs the phases that are warranted. She does not model capabilities to a depth no decision requires. She does not maintain ArchiMate views nobody reads. She discarded the parts of the frameworks that served the frameworks rather than the organisation, and she discarded them without guilt, because she had stopped valuing being right about the frameworks and started valuing helping Meridian decide well.

What she learned: the gap between the frameworks she was trained in and the practice she actually built. The training had taught her the maps as though mastering them were the job. The practice taught her that the job was the territory — the dual EPR, the unowned identity, the frightened clinician, the rational project leader, the rising VMware bill — and that the maps were valuable exactly insofar as they helped her navigate it and worthless when she served them instead. The most important thing she learned was not in any framework: that her effectiveness came from staying connected to the reality in front of her, using the maps to read it rather than to replace it.

The book ends with her, three years in, neither the framework purist she was trained to be nor the framework sceptic that disillusionment might have made her, but something more useful than either: a practitioner who uses the maps fluently and is never fooled into mistaking them for the territory. That is what this book has been trying to make possible — not for her, who is fictional, but for you, who are not.

The Closing Argument

Reading the Map set out to teach the territory architects work in — the frameworks, the concepts, the diagrams, the language, and the organisational reality — so that when you decide to go deeper, you are not starting from confusion. It did not try to make you an architect. It tried to make you literate in the world architects navigate, on the conviction that literacy is what lets you follow the conversations, ask the sensible questions, recognise what is being decided, and contribute from wherever you sit.

The conviction underneath all of it is the one this chapter ends on. The frameworks are a map, not the territory. They are genuinely valuable — a good map is worth a great deal in unfamiliar country — but they are valuable only as instruments for navigating something real. The territory is the organisation in front of you, the people in the room, and the problem that needs solving today. No framework is recommended over another in these pages, and no path is prescribed, because the right framework and the right path depend entirely on the territory you are standing in, which only you can see.

You now have the map-reading skills. Where you go with them is yours to choose. That was always the point: not to tell you the way, but to make sure that when you set out, you can read the map — and never forget that it is only a map.

Translator Panel

The captured architect says: “We need to complete the model and run the full process.” > What that means: The framework has become the goal. Completeness and process are being pursued for their own sake rather than because they improve a decision — the map substituting itself for the territory. The grounded response is to ask what decision this completeness would improve, and to stop when the answer runs out.

The grounded architect says: “Which part of this framework actually helps us decide better, here, now?” > What that means: The framework is kept in its place as an instrument, applied selectively in service of the real problem. The territory — the organisation, the people, the decision — is held as the thing that matters, and the framework is valued exactly insofar as it helps navigate it.

The Key Idea

The book closes on the discipline everything else depends on: using the frameworks without being used by them. The frameworks exert a gravitational pull toward themselves — toward ceremony, completeness, and the seductive feeling that modelling something means understanding it — and the deepest form of the pull is the architect who comes to value being right about the frameworks rather than helping the organisation decide well. Staying grounded means keeping the frameworks as instruments: asking what each one is for here and now, letting reality win when the model and the territory disagree, staying close to delivery, and preferring the useful to the complete. For those who come from delivery, it means keeping the delivery instincts alive alongside the architectural vocabulary, because the instinct that asks “what happens when the dependency slips?” is worth more than the roadmap. The frameworks are a map; the territory is the organisation in front of you, the people in the room, and the problem that needs solving today; and the whole purpose of this book has been to give you the map-reading skills while making sure you never mistake the map for the territory.

Next: The appendices follow — the glossary, the framework comparison, the ADM phase reference, the diagram reading guide, the professional landscape, and the honest further-reading list — reference material to support the navigation this book has taught.