In short: TOGAF (The Open Group Architecture Framework) is the de-facto standard framework for enterprise architecture. Its heart is the ADM (Architecture Development Method) – an iterative cycle that takes an organisation methodically from its current to its target architecture, with governance built in. TOGAF answers the question “How do we do enterprise architecture systematically?” This article explains what TOGAF is, how the ADM works, what certification means, and – from our experience in real Portamus client projects – when TOGAF is the right choice and when it needs tailoring.
Key takeaways
- TOGAF is a method/framework, maintained by The Open Group, and the world’s most widely adopted EA framework.
- Its core is the ADM – phases A–H around continuous Requirements Management.
- TOGAF describes the process; it deliberately prescribes no modelling notation – which is where ArchiMate fits in.
- TOGAF is adaptable: the ADM should be tailored to the organisation, not applied by rote.
- Certification (Foundation, Practitioner) proves knowledge of the standard; results depend on experienced application.
What is TOGAF?
TOGAF is the de-facto standard framework for enterprise architecture, maintained by The Open Group. It provides a structured, repeatable approach to planning, designing, governing and evolving the architecture of an organisation across business and IT. Rather than a rigid rulebook, TOGAF is a method plus a supporting toolkit that architecture teams tailor to their context.
TOGAF provides, among other things:
- the ADM as a process model (phases A–H),
- a Content Framework defining which deliverables and artefacts are produced,
- an Enterprise Continuum and reference models for classifying and reusing architecture assets,
- governance and stakeholder concepts to keep architecture decisions accountable.
What TOGAF deliberately does not prescribe is a concrete notation for the models themselves – which is exactly where a modelling language such as ArchiMate comes in. We compare the two in TOGAF vs. ArchiMate.
The ADM: the heart of TOGAF
The Architecture Development Method (ADM) is what most people mean when they talk about “doing TOGAF”. It is an iterative cycle – not a one-off waterfall – that continuously evolves the architecture:
| Phase | Focus |
|---|---|
| Preliminary | Establish the architecture capability, principles and governance |
| A – Architecture Vision | Scope, stakeholders, goals and a high-level vision |
| B – Business Architecture | Capabilities, processes, organisation |
| C – Information Systems Architecture | Data and application architecture |
| D – Technology Architecture | Infrastructure, platforms, networks |
| E – Opportunities & Solutions | Identify and group the work needed |
| F – Migration Planning | Sequenced, prioritised roadmap |
| G – Implementation Governance | Ensure delivery matches the architecture |
| H – Architecture Change Management | Manage change and feed the next cycle |
At the centre sits Requirements Management, which feeds and is fed by every phase. In our client projects this central role of requirements is decisive: it keeps the architecture anchored to what the business actually needs, cycle after cycle.
Rule of thumb: TOGAF’s ADM tells you which steps to take to move from today’s architecture to a defensible target – and how to govern that journey.
TOGAF certification
The Open Group offers a formal certification programme, typically in two levels:
- TOGAF Foundation – knowledge of the terminology, structure and core concepts.
- TOGAF Practitioner – the ability to apply the ADM and concepts in practice.
For individuals – architects, consultants, project leads – certification is a widely recognised credential and a shared vocabulary. For organisations, the more important question is competent, tailored application. In our experience the same standard delivers very different results depending on who applies it and how well they adapt it – which is why we treat certification as a foundation, not a guarantee.
When TOGAF is the right choice
From our advisory practice, TOGAF fits especially well when:
- you need a structured, governable process for enterprise architecture, not ad-hoc diagrams;
- you are driving a major transformation (cloud, ERP replacement, consolidation, AI adoption) and need a defensible roadmap;
- multiple teams must work to a common method and vocabulary;
- you want architecture to be a continuous steering capability, not a one-off document.
And where it needs care:
- TOGAF is not a modelling notation – pair it with ArchiMate for consistent models;
- applied by rote, the full ADM can feel heavyweight – tailoring is mandatory, especially in mid-sized organisations. In our projects we consistently scope the ADM to the organisation’s size and maturity.
Common misconceptions
- “TOGAF is too heavyweight for us.” → TOGAF is adaptable; the ADM is meant to be tailored. Right-sized, it works for the mid-market too.
- “TOGAF is a modelling tool.” → No. TOGAF is a method; it prescribes no notation. Use ArchiMate for the models.
- “Certification equals capability.” → Certification proves knowledge of the standard; delivering value depends on experienced, tailored application.
- “TOGAF and Agile don’t mix.” → They do. The ADM is iterative by design and integrates well with agile delivery when scoped sensibly.
TOGAF and enterprise architecture management
TOGAF is the leading method within the broader discipline of Enterprise Architecture Management (EAM) – the ongoing practice of aligning business and IT and steering their evolution. TOGAF supplies the how; EAM is the management practice that keeps the architecture alive and used for decisions. In the age of agentic AI, that steering capability matters more, not less: autonomous systems need clear principles, permitted actions and human-in-the-loop points – all of which TOGAF’s Preliminary/Phase A principles and Requirements Management are built to provide.
Conclusion
TOGAF is the proven, adaptable method for enterprise architecture: a structured, iterative way – via the ADM – to move an organisation from its current to its target architecture, with governance built in. It is not a notation and not a rigid rulebook; its value depends on tailoring it wisely and applying it with experience. Our consistent experience from Portamus client projects: combine TOGAF as method with ArchiMate as modelling language, right-size it to your organisation, and you get an architecture that is genuinely steerable – not merely documented.
Want to introduce or tailor TOGAF in your organisation? We guide you from method selection to a working, governed architecture practice. → Discover Portamus Enterprise Architecture consulting