Zachman vs TOGAF in Practice: How Different Organizations Use Each Framework

TOGAF is used as the EA process: the Architecture Development Method phases, the governance gates, the stakeholder engagement approach, the deliverable set. Zachman is used as the artifact taxonomy: whether a given document addresses the Executive perspective or the Architect perspective, the How interrogative or the Why. Most serious programs use TOGAF for method and Zachman as a completeness check. TOGAF Phase B produces business architecture deliverables; Zachman tells you whether those deliverables cover all the stakeholder perspectives a complete business architecture should address.

Two roles, side by side

---

Real-world adoption patterns

Large enterprises: TOGAF primary, ArchiMate notation

Large commercial enterprises — financial services, telecoms, global manufacturers — most commonly adopt TOGAF as the primary framework. The ADM provides the process the EA team follows; ArchiMate provides the modeling notation; and the Architecture Repository stores the outputs in Sparx EA under TOGAF-aligned governance (phase tagging, Architecture Building Block / Solution Building Block distinction, Architecture Decision Records).

Here, Zachman appears in one of two forms. Either EA leadership uses it to audit artifact completeness — checking that the TOGAF-governed program covers all perspectives — without making it visible to the broader team. Or it’s absent entirely, with the TOGAF deliverable set treated as sufficient. The enterprises that get the most from Zachman are those running active EA maturity programs, where the population matrix becomes valuable maturity evidence.

Government agencies: FEAF mandate, Zachman alignment

US federal agencies operate under the OMB EA mandate and FEAF, which supplies the reference domains (Business, Data, Applications, Infrastructure, Security, Performance) and the investment-alignment methodology. State and local agencies may use FEAF as a reference or adopt TOGAF independently. UK central government works under the Government Digital Service Technology Code of Practice and NCSC guidance — often with TOGAF-trained teams but no mandated framework equivalent to FEAF.

In government, Zachman supplies the stakeholder-perspective completeness layer that mandated artifacts need to demonstrate. Agencies under OMB oversight or departmental audit benefit from the population matrix as evidence that the program addresses all required perspectives, not just the technical layers IT-focused teams gravitate toward.

Academic and research institutions: Zachman for completeness rigor

Universities, research councils, and national laboratories often find Zachman valuable in its own right, independent of TOGAF — partly because its ontological rigor appeals to institutional cultures that value theory, and partly because academic EA is often a classification and documentation exercise rather than an ongoing governance function. Zachman gives them a structured way to organize architecture knowledge across data assets (What), administrative processes (How), campus and cloud infrastructure (Where), and organizational structure (Who). TOGAF’s ADM, which assumes continuous governance, can be a less natural fit for the cyclical, project-based nature of university work.

Consulting firms: TOGAF process, ArchiMate delivery, Zachman check

Consultancies that deliver EA engagements most commonly use TOGAF as the engagement process and ArchiMate as the delivery notation. Within practice, Zachman functions as a quality-assurance tool: before handing a completed deliverable set to a client, consultants with Zachman training can quickly assess whether the artifacts cover all the perspectives the client’s governance will require. An engagement that delivers comprehensive Phase B content only at the Row 3 Architect perspective — with no Row 1 Executive or Row 2 Business Management artifacts — won’t serve the client’s senior stakeholders, however technically rigorous the Row 3 content is.

---

The hybrid: TOGAF process with Zachman audit

The hybrid — the approach most recommended for serious programs — uses TOGAF as the method and Zachman as the completeness audit. It works in four moves:

1. TOGAF ADM phases proceed normally. Phase A through the governance phases, deliverables produced to the TOGAF standard and stored in Sparx EA with phase tags.
2. At each phase completion, a Zachman audit runs. The team reviews the phase’s deliverables and asks: for each Zachman cell this phase should address, did we produce an artifact? A Phase B audit asks whether Business Architecture artifacts exist at Row 1, Row 2, and Row 3 for the How and Who columns.
3. Gaps are addressed before the gate. If Row 2 How artifacts are missing — functional managers have no process documentation at the right level — that gap is closed before the phase is declared complete and the Architecture Review Board gate is approached.
4. The population matrix is updated. As gaps fill, the matrix reflects the coverage. At program completion it demonstrates artifact completeness to oversight authorities or internal reviewers.

The hybrid fixes a real limitation of TOGAF without abandoning it. The ADM is phase-structured and deliverable-oriented, but it doesn’t inherently guarantee that deliverables cover all perspectives. A TOGAF-compliant program can produce excellent Architecture Definition Documents oriented entirely to Row 3 and Row 4 — useful for architects and engineers, inaccessible to executives and mission owners. It passed its gates but failed to produce the architecture business stakeholders need. Zachman’s row structure forces the question: for every domain, have we produced artifacts at the perspective of the people who actually use them?

---

Implementing the hybrid in Sparx EA

In Sparx EA, the hybrid works by adding Zachman tagged values to existing TOGAF Deliverable elements. The TOGAF Deliverable stereotype already carries phase, status, and type tags; Zachman row and column tags are added to the same profile. The two-level classification (primary and secondary perspective) handles the reality that most artifacts address more than one cell — the Application Architecture Document is primarily a Row 3 (Architect) artifact but has Row 4 (Engineer) implications in its technical detail.

Once deliverables are tagged, Sparx EA’s search and matrix features support coverage queries:

• Filter by zachman_row = Row 2 and zachman_column = How to find all Business Management process artifacts — or confirm their absence.
• Generate a Relationship Matrix with Zachman rows on one axis and columns on the other, cells populated by the tagged artifacts.
• Use a custom report to produce the full population matrix as a governance document.

These queries run against the live repository and reflect the current artifact set — making coverage a live governance view rather than a periodic stocktake.

Why it helps when the repository feeds AI

A Zachman-tagged repository is also more useful when it’s connected to AI tools, because natural-language questions from business stakeholders map cleanly onto Zachman interrogatives:

• “What data does our customer service department use?” → What column, Who perspective, Row 2
• “How does the mortgage application process work?” → How column, Row 2
• “Where are our customer data systems hosted?” → Where column
• “Who is responsible for the credit-risk system?” → Who column, Row 1/2
• “Why are we investing in the new CRM platform?” → Why column, Row 1/2

When those questions arrive through an AI interface connected to the repository, Zachman tags let the answer be filtered to the right stakeholder perspective. A business director asking about HR data systems gets Row 1/2 business-level artifacts — capability maps, plain-language process descriptions — rather than the Row 4 database schema that is technically the most complete answer but not what they need. That filtering is what makes AI responses genuinely useful to non-technical stakeholders, and the tagging is what makes the filtering possible.

---

Frequently asked questions

---

Implement the framework combination your program needs

Framework debates matter less than getting the right artifacts to the right stakeholders at the right time. TOGAF provides the process; Zachman identifies the gaps; Sparx EA governs both. If you’re not sure where your program stands today, the practical move is an assessment — exactly the structured starting point our work with architecture leaders begins from, before adding Zachman completeness to an existing TOGAF program.