There is a particular kind of online discourse where someone says “TOGAF is useless” and the replies split between people who agree on the basis of a single bad experience and people who disagree on the basis of a certification they took eight years ago. Almost no one in the thread has read the current standard. I decided to be the person who had.

The 10th Edition, published in 2022 and lightly updated since, is a genuine restructuring of the framework. It is not the same TOGAF the internet remembers. Whether the restructuring is enough to recover the reputation is a different question, which I will come back to.

The standard is published as a set of volumes. The link above is the entry-point volume — Introduction and Core Concepts — which is what most practitioners actually need. The other volumes (ADM, ADM Practitioners’ Guide, Architecture Content, Series Guides) are available separately. The Open Group’s own bookstore at publications.opengroup.org carries the full set if you want them all in one place.

What changed in the 10th Edition

The big structural change is the split into the TOGAF Fundamental Content and the TOGAF Series Guides. The Fundamental Content is the small, stable core: the ADM, the Architecture Content Framework, the Enterprise Continuum, and the foundational concepts. The Series Guides are the larger, evolving body of material on specific topics — agile and the ADM, the digital enterprise, data architecture, security, business architecture, and so on.

This split is the most useful thing The Open Group has done with the standard in fifteen years. The Fundamental Content is now small enough that a practicing architect can actually read it in a weekend. The Series Guides are explicitly optional and explicitly composable — you take the ones that match your operating context and ignore the rest.

In practical terms, this means the answer to “do I have to do all of TOGAF” is now formally “no.” Which is what experienced practitioners were already telling each other, but the standard now backs them up.

The ADM, honestly

The Architecture Development Method remains the heart of the standard, and remains the part that draws the most criticism. Most of the criticism is deserved when the ADM is applied as a literal sequential process and undeserved when it is applied as a cyclic checklist of concerns. The 10th Edition leans harder than previous editions on the second framing. The phases — Preliminary, Vision, Business, Information Systems, Tech, Opportunities, Migration Planning, Implementation Governance, Change Management — are presented as questions to answer, not deliverables to produce.

In a healthy EA practice the ADM functions roughly as the Architecture equivalent of a code review checklist. You do not literally walk through every item every time, but the list exists so that nothing important quietly drops off the agenda.

The unhealthy alternative — producing a hundred-page Architecture Definition Document because the framework allegedly demands it — is the caricature most TOGAF critics are reacting to, and the standard now quietly disowns this. Whether your organization’s TOGAF-trained consultants have got the message is a separate matter.

The Series Guides are where the real content lives

If you only read the Fundamental Content, you will come away thinking TOGAF has remarkably little to say about anything specific. That is by design. The Series Guides are where the framework engages with concrete domains:

  • Agile and the ADM is the one most practitioners need. It is also the one most consultants ignore. It explicitly endorses lightweight, iterative architecture work and pushes back against the big-up-front-design caricature.
  • The Digital Enterprise is a reasonable, if slightly conservative, framing of how EA needs to change as products go digital. Nothing shocking but a useful shared vocabulary.
  • Business Architecture: A Practitioners’ Guide is the bridge between TOGAF and the BIZBOK-style business architecture world. Genuinely useful if you are trying to make capability mapping land in a TOGAF shop.
  • Information Architecture is fine. The data-architecture community has largely moved on, but if you need a TOGAF-compatible vocabulary for talking to a CDO, it does the job.

There are dozens of Series Guides. You will not read them all. You should not try to.

What TOGAF still does badly

Three things.

  • Tooling. The standard is studiously tool-agnostic, which sounds virtuous but means that every TOGAF practice has to reinvent the question of how to actually maintain the artifacts. The result is a cottage industry of EA tooling vendors selling solutions to a problem the standard refuses to acknowledge.
  • Outcome measurement. TOGAF tells you how to do architecture work but says very little about how to know whether the architecture work worked. Series Guide on “EA capability” gestures at this. It is not enough.
  • Modern delivery models. Despite the Agile Series Guide, the underlying ADM still assumes a delivery model where there is a reasonably stable target state to migrate toward. In a product-led organization with continuously evolving capabilities, that assumption is shakier than the framework admits.

Who should actually read it

  • Anyone preparing for OGEA-101 (the Foundation exam). Read the Fundamental Content. You do not need most of the Series Guides.
  • Anyone preparing for OGEA-102 (the Practitioner exam). Read the Fundamental Content plus the Series Guides on Business Architecture, Digital Enterprise, and Agile.
  • Practising architects in a TOGAF-shaped organization who want a shared vocabulary with their stakeholders.
  • New heads of EA who want to know what their predecessor’s framework actually says before they accept or reject it.

I would not recommend it to:

  • A startup architect. The framework is designed for organizations with governance overhead. Most of TOGAF is solving problems you do not have.
  • A platform engineer. The altitude is wrong.

Reading note

If you are going to read it, get the print edition. The PDF is searchable but the framework is structurally recursive in a way that makes flipping back and forth necessary. The Open Group’s own bookstore is the canonical source. Used copies of the 9.2 edition are not a substitute; the structural changes in 10 matter.

Bottom line

The 10th Edition is the first version of TOGAF that I would actively defend to a sceptical practitioner. The Fundamental Content is small enough to be honest about what it does and does not promise; the Series Guides are explicit about being optional; the ADM is finally framed as a checklist rather than a waterfall.

It is still not the only thing you should read. Pair it with Enterprise Architecture As Strategy for the operating-model lens it presupposes, and with Mastering TOGAF 10 if you need a study-companion that actually engages with the exam questions.

I have also written a longer TOGAF 10 self-study path for people preparing for OGEA-101 and OGEA-102, which includes the order I recommend reading things in and how I would budget the time.