TOGAF Explained: The ADM, Domains and How to Use It

Strategy-to-execution alignment

Enterprise architecture creates leverage when strategic priorities are translated into capability-level outcomes and delivery sequencing.

This requires a shared language between executives, architecture leaders, and delivery organizations.

• Define measurable capability outcomes tied to strategic goals
• Map cross-domain dependencies before portfolio commitment
• Review architecture assumptions at each roadmap increment

What TOGAF is — and what it is not

TOGAF is an enterprise architecture framework maintained by The Open Group, a vendor-neutral standards body. In plain terms, it is a shared method and vocabulary that lets an organisation plan, design, govern and evolve its architecture in a consistent way, rather than reinventing the approach for every project.

It helps to say what TOGAF is not. It is not a software product, not a certification you must hold to begin, and not a rigid recipe. It is a body of guidance — most visibly a process called the ADM — that teams adapt to their context. The rest of this primer paraphrases the core ideas; the authoritative source is The Open Group's own standard.

The ADM: a cycle, not a checklist

The heart of TOGAF is the Architecture Development Method, or ADM — a cyclical process for moving from strategy to delivered change and back again. It is deliberately iterative: you revisit phases as you learn, rather than marching once through a linear plan.

At a high level the ADM runs from a preliminary set-up, through an architecture vision, into the architecture domains, then into opportunities, migration planning, governance and change management. The diagram on this page sketches the cycle. The value is less in the exact phase names and more in the discipline: agree the vision, describe current and target states, plan the move, govern the implementation, and feed lessons back in.

• Preliminary and Architecture Vision: scope, principles and the case for change
• Business, Data, Application and Technology architectures: current and target states
• Opportunities, Solutions and Migration Planning: how to get there
• Implementation Governance and Change Management: keep it on track and current

The four architecture domains

TOGAF organises architecture into four interrelated domains. The business architecture describes capabilities, processes and organisation. The data (or information) architecture describes the data the business relies on. The application architecture describes the applications and how they support processes. The technology architecture describes the infrastructure and platforms underneath.

The domains are not silos; their value is in the links between them — which capability a process supports, which applications hold which data, which technology a given application runs on. Keeping those relationships explicit is what lets you reason about change instead of guessing at its blast radius.

Framework versus certification

A common confusion: using TOGAF and being TOGAF-certified are different things. The framework is freely usable to structure your practice. Certification, offered by The Open Group, validates an individual's knowledge of the standard and can help with consistency and credibility — but you do not need every architect certified to start applying the ADM and the domains.

Be wary of any tool that claims to make you "TOGAF-compliant" as if that were a binary stamp. What tools can honestly do is support a TOGAF-aligned practice: hold the artefacts, structure the phases, and keep the model current.

How to apply TOGAF pragmatically with Archilu

Most organisations get value from TOGAF by adopting it selectively: use the ADM to structure a real piece of work, use the four domains to organise the model, and use a shared vocabulary so business and IT discuss the same thing. You do not need to implement every artefact the standard describes on day one.

Archilu supports a TOGAF-aligned practice without claiming any certification: it holds the business, application, data and technology layers in one connected model, supports the review and governance steps the ADM calls for, and keeps everything current so the architecture stays a living asset rather than a document. To see where to start, Archilu's free EA maturity assessment scores ten dimensions and returns a prioritised plan in about ten minutes, and the linked TOGAF tool guide and ADM checklist turn the method into concrete next steps. TOGAF is a trademark of The Open Group.

Execution alignment KPIs

These indicators show whether architecture is improving strategic execution quality.

• Capability outcome attainment vs roadmap target
• Strategic initiative delay caused by architecture dependencies
• Architecture debt trend on critical value streams
• Portfolio re-prioritization speed after risk change

Common mistakes

Strategic architecture work fails when it is disconnected from delivery sequencing and budget decisions.

• Publishing target states without execution ownership
• No dependency mapping across initiatives
• No cadence for architecture refresh based on outcomes
• No explicit link between architecture debt and portfolio risk