Reading the Map · Reference
The honest reading list, organised by chapter. For each area: the primary official source, the most useful practitioner resource, and one honest sentence about what each gives you. This is deliberately short per entry — a curated path, not an exhaustive bibliography. Where a chapter’s own Further Reading section already lists specific titles, this appendix gives the through-line rather than repeating every entry.
Part 1 — What Is Enterprise Architecture (Chapters 1–3)
Primary source: The Open Group, TOGAF Standard introduction (opengroup.org) — for the mainstream account of what EA is and where it came from.
Most useful practitioner resource: Gregor Hohpe, The Software Architect Elevator (O’Reilly, 2020) — the single most useful book in this whole list for understanding what architects actually do in organisations.
Honest note: the official sources tell you what EA is supposed to be; Hohpe tells you what it is.
Part 2 — The Frameworks Explained (Chapters 4–15)
Zachman: John Zachman’s own material at zachman.com — the taxonomy from its author. Gives you the classification idea; will not tell you how to build anything.
TOGAF & the ADM: The Open Group, TOGAF Standard, 10th Edition (opengroup.org) — the method itself. Read the ADM phase summaries; apply selectively (Appendix C).
ArchiMate: Gerben Wierda, Mastering ArchiMate (R&A, 3rd ed. 2017) — the best practitioner guide. Honest about which parts of the notation earn their keep.
SABSA: the SABSA Institute material and Sherwood et al., Enterprise Security Architecture — the coherent treatment of security as architecture, not checklist.
BIZBOK / business architecture: Business Architecture Guild, BIZBOK Guide — the authority on capabilities and value streams; abstract until applied.
Wardley Mapping: Simon Wardley, Wardley Maps (free, medium.com/@swardley) — the most alive idea in the field, given away free.
ITIL & COBIT: the official Axelos (ITIL 4) and ISACA (COBIT) foundations — the operating and governance frames that sit downstream of architecture.
Honest note: you do not need to read all of these. Read the one closest to the problem in front of you; the others make more sense once you have used one in anger (Chapter 21).
Part 3 — The Core Concepts (Chapters 16–33)
BDAT and the domains: The Open Group, TOGAF Standard, Phases B–D — the domain structure; light on the level-of-detail discipline this book stresses.
Capability mapping: Business Architecture Guild BIZBOK and Jeff Scott’s capability writing — the how and why of capability models.
Architecture & technical debt: Neal Ford, Rebecca Parsons & Patrick Kua, Building Evolutionary Architectures (O’Reilly, 2017) — the clearest account of how decisions constrain the future.
Portfolio & the 6Rs: Gartner’s TIME model and AWS’s “6 Strategies for Migrating Applications” — the disposition frameworks; read the cloud-vendor one critically.
Governance: Hohpe, The Software Architect Elevator again, on architecture as a control system — the antidote to Architecture Theatre.
Patterns: Gregor Hohpe & Bobby Woolf, Enterprise Integration Patterns (Addison-Wesley, 2003) and Mark Richards & Neal Ford, Fundamentals of Software Architecture (O’Reilly, 2020) — the catalogues of recurring shapes and their failure modes.
The organisational reality: Hohpe (again) and, uncomfortably, Machiavelli’s The Prince — why being right is not enough (Chapter 32).
Honest note: Part 3 is where the book’s own argument lives; the reading here deepens it rather than replacing it.
Part 4 — Reading the Diagrams (Chapters 34–41)
The notations: Martin Fowler, UML Distilled (Addison-Wesley, 3rd ed. 2003) for sequence, component, and activity diagrams — exactly the reader-not-producer level you need. Simon Brown’s C4 model (c4model.com) for component-level clarity.
ArchiMate views: Wierda, Mastering ArchiMate (again) — the relationships chapters are what a reader benefits from most.
Zachman cells: Zachman’s own material (zachman.com) — the grid, read as perspectives rather than artefacts to produce.
Wardley maps: learnwardleymapping.com — the gentlest route to reading competence.
The reading discipline: Edward Tufte, The Visual Display of Quantitative Information (Graphics Press, 2nd ed. 2001) — on reading any diagram critically and spotting where visual confidence outruns content.
Honest note: diagram reading is a practice, not a theory; read a few real diagrams with the techniques from these chapters and the skill builds fast.
Part 5 — The Language Map (Chapters 42–45)
On communication: Chip & Dan Heath, Made to Stick (Random House, 2007) and Steven Pinker, The Sense of Style (Viking, 2014) — why expert vocabulary fails to communicate, and how to fix it.
On the budget conversation: Douglas Hubbard, How to Measure Anything (Wiley, 3rd ed. 2014) — attaching credible numbers to the cost of inaction (Chapter 44).
On tailoring to audience: Aristotle’s Rhetoric and Fisher & Ury, Getting to Yes (Penguin, 3rd ed. 2011) — the ancient and modern cases for meeting the audience where they are, honestly.
Honest note: language discipline is the most learnable of the architect’s skills and the most neglected; these are worth more time than their apparent distance from “real” architecture suggests.
Part 6 — Navigating the Territory (Chapters 46–50)
On EA thinking from any role: Donella Meadows, Thinking in Systems (Chelsea Green, 2008) — the system-seeing habit, accessibly.
On asking questions: Edgar Schein, Humble Inquiry (Berrett-Koehler, 2nd ed. 2021) — the tone and craft of the question that contributes rather than challenges.
On contributing without the title: Will Larson, Staff Engineer (2021) — influence and visible thinking without management authority.
On the first 90 days: Michael Watkins, The First 90 Days (HBR Press, updated ed. 2013) — the listen-before-acting discipline, almost wholesale applicable.
Honest note: this part is about you, not the frameworks; the reading is about influence, communication, and transition, because that is what the part is about.
Part 7 — The Practitioner’s Compass (Chapters 51–54)
de Visscher (connection over control): his published work and talks; supplement with Hohpe’s Elevator and Niels Pflaeging, Organize for Complexity (BetaCodex, 2014) — why connection-based coordination beats control-based.
Dooher (the architect as educator): his work on the intent gap; supplement with L. David Marquet, Turn the Ship Around! (Portfolio, 2013) — transmit-intent over give-orders, demonstrated at sea.
Davis (AI and the capability model): his writing on People-Process-Technology-AI; supplement with Stuart Russell, Human Compatible (Viking, 2019) — designing meaningful human control of AI.
Staying grounded: Donald Schön, The Reflective Practitioner (Basic Books, 1983) and the origin of “the map is not the territory” in Korzybski — the discipline the whole book rests on.
The Companion Framework
The OrdoAnimi Framework — framework.ordoanimi.com. Where this book teaches you to read the territory, the OrdoAnimi is one considered argument about how to do architecture well within it. It is the intended sequel for readers ready to go deeper — the framework that becomes relevant once you can read the map.
A Closing Word on Reading
The honest meta-note for this entire list: reading about architecture is not the same as practising it, and no amount of the former substitutes for the latter. These books and standards are maps of maps. They are genuinely useful — a good map saves you from many wrong turns — but they are valuable only insofar as they help you navigate real organisations, real people, and real decisions. Read selectively, in service of the territory in front of you, and never mistake having read the map for knowing the ground.