Direct Answer
TOGAF is used as the EA process — how we do architecture: the Architecture Development Method phases, the governance gates, the stakeholder engagement approach, the deliverable set. Zachman is used as the artefact taxonomy — how we classify what we produce: whether a given architecture document addresses the Executive perspective, the Architect perspective, the How interrogative or the Why interrogative. Most serious EA programmes use TOGAF for method and Zachman as a completeness check. The two frameworks are complementary, not competing: TOGAF ADM Phase B produces business architecture deliverables; Zachman tells you whether those deliverables cover all the stakeholder perspectives a complete business architecture should address. In Sparx EA, TOGAF-governed repositories add Zachman tagged values to existing TOGAF Deliverable elements without restructuring the primary governance model. A Zachman-tagged repository also enables AI augmentation — natural language questions from business users map naturally to Zachman interrogatives, improving the quality of AI responses from an EA GraphLink-connected repository.
Real-World Framework Adoption Patterns
Large Enterprises: TOGAF Primary, ArchiMate Notation
Large commercial enterprises — financial services firms, telecommunications operators, global manufacturing organisations — most commonly adopt TOGAF as their primary EA framework. The TOGAF ADM provides the process that EA teams follow; ArchiMate provides the modelling notation that makes architecture diagrams consistent and interpretable; and the Architecture Repository stores the outputs in Sparx EA with TOGAF-aligned governance (phase tagging, Architecture Building Block / Solution Building Block distinction, Architecture Decision Records).
In large enterprises, Zachman typically appears in one of two forms. Either it is used by the EA leadership to audit artefact completeness — checking whether the TOGAF-governed programme has produced artefacts that cover all stakeholder perspectives — without being visible to the broader architecture team. Or it is absent entirely, with the TOGAF deliverable set treated as sufficient for completeness without the meta-level Zachman check.
The organisations that get the most value from Zachman in a large enterprise context are those with EA maturity programmes: organisations that are actively assessing and improving their EA practice, not just running it. The Zachman population matrix is a valuable maturity evidence artefact.
Government Agencies: FEAF Mandate, Zachman Alignment
US federal government agencies operate under the OMB EA mandate and the Federal Enterprise Architecture Framework (FEAF). FEAF provides the reference architecture domains (Business, Data, Applications, Infrastructure, Security, Performance) and the investment alignment methodology. State and local government agencies in the US may use FEAF as a reference or may adopt TOGAF independently.
UK central government agencies work under the Government Digital Service (GDS) Technology Code of Practice and the National Cyber Security Centre (NCSC) guidelines, often with TOGAF-trained EA teams but without a mandated EA framework equivalent to FEAF.
In government contexts, Zachman provides the stakeholder perspective completeness layer that FEAF-mandated artefacts need to demonstrate. Government agencies subject to OMB oversight or departmental audit benefit from the Zachman population matrix as evidence that their architecture programme addresses all required stakeholder perspectives, not just the technical architecture layers that IT-focused EA teams naturally gravitate towards.
Academic and Research Institutions: Zachman for Completeness Rigour
Academic and research institutions — universities, research councils, national laboratories — often find Zachman valuable in its own right, independent of TOGAF. This is partly because Zachman’s academic rigour (the framework is a formal ontology) appeals to institutional cultures that value theoretical rigour, and partly because academic institutions often approach EA as a classification and documentation exercise rather than as an ongoing governance function.
For academic EA programmes, Zachman provides a structured way to organise architecture knowledge: the university can classify its data assets (What column), its administrative processes (How column), its campus and cloud infrastructure (Where column), and its organisational structure (Who column) across the stakeholder perspective hierarchy. TOGAF’s ADM process, which assumes ongoing architectural governance, may be less well suited to the cyclical, project-based nature of university EA work.
Consulting Firms: TOGAF Process, ArchiMate Delivery, Zachman Check
Consulting firms that deliver EA engagements most commonly work with TOGAF as the engagement process and ArchiMate as the delivery notation. Clients who do not have a preferred framework receive a TOGAF-aligned engagement; clients with an existing FEAF or Zachman preference receive a correspondingly adapted approach.
Within consulting practice, Zachman functions as a quality assurance tool: before submitting a completed EA engagement deliverable set to a client, consultants with Zachman training can rapidly assess whether the artefact set covers all the stakeholder perspectives the client’s governance will require. A consulting engagement that delivers comprehensive Phase B (Business Architecture) artefacts only at the Row 3 Architect perspective — and lacks Row 1 Executive and Row 2 Business Management artefacts — will not serve the client’s senior stakeholders, regardless of how technically rigorous the Row 3 content is.
The Hybrid Approach: TOGAF Process with Zachman Audit
How the Hybrid Works
The hybrid approach — the one most recommended for organisations with serious EA programmes — uses TOGAF as the architectural method and Zachman as the completeness audit mechanism. It works as follows:
- TOGAF ADM phases proceed normally: Phase A (Architecture Vision), Phase B (Business Architecture), Phase C (Information Systems Architecture — Applications and Data), Phase D (Technology Architecture), and the governance phases that follow. Deliverables are produced per the TOGAF documentation standard, stored in the Sparx EA repository with TOGAF phase tags.
- At each ADM phase completion, a Zachman audit is run: The EA team reviews the deliverables produced in the phase and asks: for each Zachman cell that this phase should address, have we produced an artefact? A Phase B completion audit asks: do we have Business Architecture artefacts at Row 1 (Executive), Row 2 (Business Management), and Row 3 (Architect) level for the How column (business processes) and the Who column (organisation and roles)?
- Gaps identified in the audit are addressed before gate review: If the Zachman audit identifies that Row 2 How artefacts are missing — that functional managers have no business process documentation at an appropriate level of detail — that gap is addressed before the phase is declared complete and the Architecture Review Board gate is approached.
- The Zachman population matrix is updated: As gaps are filled, the matrix reflects the completed coverage. At programme completion, the matrix demonstrates the artefact completeness of the EA work to oversight authorities or internal reviewers.
Why the Hybrid Adds Value
The hybrid approach addresses a real limitation of TOGAF without needing to abandon it. TOGAF’s ADM is phase-structured and deliverable-oriented, but it does not inherently guarantee that deliverables cover all stakeholder perspectives. A TOGAF-compliant programme can produce technically excellent Architecture Definition Documents that are entirely oriented to Row 3 and Row 4 perspectives — useful for architects and engineers, but inaccessible to business executives and mission owners. The programme passed its TOGAF gate reviews but failed to produce the architecture that business stakeholders need.
Zachman’s row structure forces the question: for every architecture domain, have we produced artefacts at the perspective of the stakeholders who actually need to use them? The answer drives artefact production decisions that TOGAF’s deliverable templates do not always surface.
Implementing the Hybrid in Sparx EA
Tagging TOGAF Deliverables with Zachman Classification
In Sparx EA, the hybrid implementation works by adding Zachman tagged values to existing TOGAF Deliverable elements. The TOGAF Deliverable stereotype already carries phase tags (togaf_phase), deliverable type tags, and status tags. Zachman tags are added to this existing profile:
“ TOGAF Deliverable: Application Architecture Document togafphase: Phase C togafstatus: Approved zachmanrow: Row 3 (primary), Row 4 (secondary) zachmancolumn: What, How “
The two-level classification (primary and secondary perspectives) handles the reality that most architecture artefacts address more than one Zachman perspective: the Application Architecture Document is primarily a Row 3 (Architect) artefact but also has Row 4 (Engineer) implications in its technical detail.
Querying Zachman Coverage in Sparx EA
Once TOGAF deliverables are tagged with Zachman values, Sparx EA’s search and matrix view features allow coverage queries:
- Filter elements by
zachmanrow = Row 2andzachmancolumn = Howto find all Business Management perspective process artefacts — or identify the absence of any - Generate a Relationship Matrix with Zachman rows on one axis and Zachman columns on the other, with cells populated by the artefact elements that carry the corresponding tags
- Use a custom report to produce the full Zachman population matrix as a governance document
These queries run against the live repository and reflect the current state of the artefact set — making the Zachman coverage view a live governance tool.
Why It Matters for AI: Zachman-Tagged Repositories Are More Queryable
A Zachman-tagged repository is significantly more useful for AI augmentation via EA GraphLink than an untagged repository. The reason is that natural language questions from business stakeholders map naturally to Zachman interrogatives:
- “What data does our customer service department use?” → What column, Who row perspective, Row 2 Business Management
- “How does the mortgage application process work?” → How column, Row 2 Business Management
- “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 AI language model queries arrive via EA GraphLink’s MCP Server, a Zachman-tagged repository can provide responses that are filtered to the appropriate stakeholder perspective. A business user asking “what data does our finance department use?” receives artefacts at Row 1/2 level (executive and business management perspective), not the Row 4 database schema that is technically the most complete answer but is not what the user needs.
This filtering by stakeholder perspective is what makes AI responses genuinely useful to non-technical business users — and Zachman tagging is what makes the filtering possible.
FAQ
What is the fundamental difference between Zachman and TOGAF?
TOGAF (The Open Group Architecture Framework) is a process framework — specifically the Architecture Development Method (ADM), which defines how to do architecture work: the phases (Architecture Vision, Business Architecture, Information Systems Architecture, Technology Architecture), the deliverables expected at each phase, the stakeholder engagement approach, and the governance gates. Zachman is a classification taxonomy — specifically a two-dimensional grid that classifies architecture artefacts by the stakeholder perspective (rows 1–6) and the interrogative (What, How, Where, Who, When, Why) they address. TOGAF tells you how to run an architecture programme. Zachman tells you whether your architecture programme has produced the right types of artefacts for the right audiences. They are complementary, not competing.
Which framework should my organisation adopt — Zachman or TOGAF?
The practical answer for most organisations is TOGAF as the primary method, with Zachman as the completeness check. TOGAF is better supported by tools (including Sparx EA’s built-in TOGAF support), has more practitioners trained in it, and provides clearer process guidance for running an EA programme. Zachman’s value is as a meta-level audit: after TOGAF-governed phases deliver their artefacts, a Zachman coverage check identifies stakeholder perspective gaps that the TOGAF deliverable set doesn’t automatically surface. Exceptions: US federal agencies mandated to FEAF may use Zachman more prominently within the FEAF context; organisations with academic or research cultures may find Zachman’s ontological rigour more appealing; organisations assessing EA maturity often find the Zachman population matrix a natural maturity metric.
Can you run Zachman and TOGAF simultaneously in Sparx EA without creating conflicting governance?
Yes — and this is the recommended approach. In Sparx EA, Zachman is implemented as an additive MDG tagging layer on top of the primary TOGAF governance model. TOGAF Deliverable elements retain their TOGAF tags (phase, status, deliverable type); Zachman tags (row and column) are added to the same elements without conflicting with the primary structure. The Zachman tags operate as a classification layer that can be queried independently of the TOGAF governance layer. Architects familiar with TOGAF continue to work within the TOGAF framework; the Zachman coverage query is a separate governance check run at phase completion or on demand. No restructuring of the primary TOGAF governance model is required.
How does a large bank typically use Zachman versus TOGAF?
A large bank typically uses TOGAF as its primary EA framework — the ADM phases, ArchiMate notation, Architecture Review Board process — with ArchiMate as the modelling language and Sparx EA as the repository. Zachman, if used at all, appears at the EA leadership level as a coverage audit: after the Technology Architecture phase, the EA lead checks whether the deliverable set addresses all relevant stakeholder perspectives (has the Board-level technology risk view been produced? has the operations team received technology impact documentation at an appropriate level of detail?). In some banks, particularly those with mature EA programmes or those subject to regulatory EA obligations (ECB supervisory expectations for internal governance), Zachman population matrices are produced as part of the annual EA programme review.
Why is Zachman particularly relevant for AI-augmented EA repositories?
Natural language questions from business stakeholders — the queries that arrive through Microsoft Copilot, Salesforce Agentforce, or other AI interfaces connected to an EA GraphLink-enabled Sparx EA repository — map naturally to Zachman interrogatives. “What data does our HR department use?” maps to What column, Who perspective. “How does the procurement process work?” maps to How column, Row 2. A Zachman-tagged repository allows EA GraphLink to filter AI responses by stakeholder perspective: a business director asking about HR data systems receives Row 2 business-level artefacts (capability maps, process descriptions, system inventories in plain language) rather than Row 4 database schemas or Row 5 configuration specifications. This filtering makes AI responses genuinely useful to non-technical stakeholders. An untagged repository returns technically complete but stakeholder-inappropriate responses to the same question.
How does Zachman apply in a government context differently from commercial enterprise?
In government, the Zachman row hierarchy maps to specific statutory and oversight stakeholder roles that have formal architecture reporting obligations: Row 1 (Executive) maps to the CIO or programme executive with OMB reporting obligations; Row 2 (Business Management) maps to the functional programme offices with mission performance accountability; Row 3 (Architect) maps to the EA practitioner responsible for the architecture deliverables. The Zachman population matrix in government becomes an oversight evidence artefact: demonstrating to OMB, an Inspector General, or a departmental CIO that the architecture programme has produced artefacts addressing all required stakeholder perspectives. In commercial enterprise, the matrix is an internal governance tool; in government, it is frequently an external accountability document.
What is the recommended starting point for an organisation that has neither Zachman nor TOGAF?
Start with TOGAF as the process framework and implement Zachman tagging from the outset. TOGAF’s ADM provides the structure needed to begin architecture work: stakeholder identification, architecture vision, domain architecture phases, and governance gates. Establishing the TOGAF-governed Sparx EA repository with TOGAF deliverable structure, and adding Zachman tags to new artefacts as they are created, means the Zachman coverage view builds naturally as the architecture programme progresses. This is significantly more efficient than running TOGAF for several years and then retrospectively applying Zachman to a large, untagged artefact set. A Discover engagement from Sparx Services will design the TOGAF-governed repository structure and establish the Zachman MDG tagging convention as part of the initial setup.
What is the recommended Sparx Services engagement for implementing the Zachman-TOGAF hybrid?
The recommended engagement is Amplify for organisations with an existing TOGAF-governed Sparx EA repository — adding Zachman tagging to existing artefacts, establishing tagging conventions, generating the initial population matrix, and identifying coverage gaps. Amplify engagements start at $45K. For organisations without an existing Sparx EA governance model, a Discover engagement first designs the TOGAF-Zachman hybrid governance model and repository structure, followed by an Amplify engagement to implement it. The Discover + Amplify path is typically $70K–$150K depending on repository size and artefact volume. Contact Sparx Services for a scoped estimate.
Next Step: Implement the Framework Combination Your EA Programme Needs
Framework debates are less important than getting the right artefacts to the right stakeholders at the right time. TOGAF provides the process. Zachman identifies the gaps. Sparx EA governs both. EA GraphLink makes the result queryable by the AI tools your stakeholders are already using.
An Amplify engagement adds Zachman completeness to your existing TOGAF programme, delivers the population matrix, and establishes the AI-ready tagging that makes your repository queryable by natural language.
Talk to Sparx Services about an Amplify or Discover engagement
Amplify starts at $45K. Discover starts at $25K. Begin with the assessment if you are not sure where your programme currently stands.
