READING THE MAP A Guide to Enterprise Architecture for Everyone in IT
A note on this draft This is Part 1 of the manuscript for Reading the Map. It contains the Introduction and the three chapters of Part 1 — What is Enterprise Architecture. Translator panels appear throughout, showing the official definition on the left and the plain English translation on the right. Read it as a reader, not as an editor. Mark what sounds wrong. Mark what sounds right. The writing will find its final shape in your response.
Introduction ## This book is for you
Somewhere in your organisation right now there is a conversation happening about architecture. About platforms and capabilities and roadmaps and target states. About what the technology estate should look like in three years and what needs to change to get there.
You might be in that conversation. You might be outside it. You might have heard the words and wondered what they actually mean. You might be the person who already understands the problems better than anyone in the room but does not yet have the language to say so in a way that lands.
It does not matter where you are starting from. Helpdesk. Developer. Systems engineer. Infrastructure specialist. Project manager. Delivery architect. If you work in IT and you want to understand how the whole thing fits together — what Enterprise Architecture actually is, what its tools do, how its frameworks connect, and how to navigate its world without a guide — this is the book that was written for you.
There are no prerequisites. No assumed knowledge. No certification required before you turn the page.
Every concept in this book is explained from the ground up. Every framework is described plainly and honestly — what it is, where it came from, what problem it solves, and where its limits are. Every piece of jargon is translated the first time it appears and collected in the glossary at the back.
How the translator panels work
Throughout this book you will see panels like the one below. On the left is the official definition — the formal language used by the frameworks, the standards bodies, and the certification programmes. On the right is the plain English translation — what it actually means, why it actually matters, how it actually works in a real organisation.
Both versions are here because you need both. The official language gives you credibility in the rooms where that language is spoken. The plain English gives you understanding that no amount of jargon can replace. Neither one is more correct than the other. They are two ways of describing the same thing, and knowing both makes you more useful in more rooms.
That is the format. You will see it on almost every major concept in the book. Left column: what the profession says. Right column: what it means.
What this book covers
Part 1 tells the honest story of Enterprise Architecture — where it came from, what it is actually for, and how to find your bearings in the landscape of frameworks that has grown up around it.
Part 2 explains every major framework in plain English alongside its official reference. Zachman. TOGAF and the ADM. ArchiMate. FEAF and DODAF. SABSA. BIZBOK. SAP EA. Wardley Mapping. ITIL and COBIT. What each one is, where it came from, what it does well, and where it reaches its limits.
Part 3 unpacks the core concepts — the ideas and tools that come up in every EA conversation. Capability maps. Architecture Vision. BDAT. Application portfolio. Gap analysis. Architecture debt. Governance. Each one gets a translator panel and a plain English explanation of why it exists.
Part 4 teaches you to read the diagrams. Not produce them — read them. Component diagrams. Sequence diagrams. ArchiMate views. Wardley maps. Architecture roadmaps. Capability maps. The visual language of the profession, made readable.
Part 5 is the language map. The full translation between delivery language, EA language, and business language. The words that unlock budget. The words that earn trust. Why precision is not the same as pretension.
Part 6 is practical navigation. How to operate in the EA world from wherever you are sitting right now — helpdesk, developer, infrastructure engineer, delivery architect. How to read an architecture conversation. How to ask better questions. How to contribute without the title.
Part 7 engages with three thinkers who are asking the most important questions about EA right now. Not to endorse or refute. To think out loud about a profession that is still working out what it is for.
The appendices contain the full glossary, a framework comparison table, the ADM phase reference, a diagram reading guide, and the further reading list — what is worth your time and what is not.
That is all this book asks of you. Curiosity. The rest is here.
PART ONE What is Enterprise Architecture The honest answer. Where it came from. What it is actually for. How to find your bearings in the landscape.
Before you can use a map, you need to understand what maps are for. Not just that they show you where things are. Why they exist. What they leave out by design. Why the same territory can be mapped differently depending on what question you are trying to answer.
Enterprise Architecture has produced a lot of maps. Frameworks. Diagrams. Methodologies. Certification programmes. It has also produced, along the way, a fair amount of territory that looks like a map but does not actually help anyone navigate.
Part 1 does not give you the map yet. It gives you the context for reading it. A short honest history of how the discipline got here. A plain answer to what it is actually for. And a clear-eyed orientation across the landscape of frameworks so you know what exists before you are asked to use any of it.