Zachman Framework Explained: The 6x6 Classification Schema

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 the Zachman Framework is

The Zachman Framework is a classification schema for the artefacts of enterprise architecture. It was originated by John Zachman in the 1980s and is stewarded today by Zachman International. In plain terms, it is a way to organise everything you might describe about an enterprise so that nothing important is missed and nothing is described twice in the wrong place.

The crucial point — and the one most often misunderstood — is that Zachman is an ontology, not a methodology. It tells you what kinds of descriptions exist and where each belongs in a structured grid. It does not tell you the process for producing them. This primer paraphrases the framework's core ideas; the authoritative source is Zachman International's own definition.

Six columns: the fundamental questions

The columns of the Zachman grid are the six interrogatives that fully describe any complex thing: What, How, Where, Who, When and Why. Applied to an enterprise, they map to data, function, network, people, time and motivation respectively.

The discipline of the columns is that they are independent. The 'What' of the business (its data and things) is a different kind of description from the 'Why' (its goals and motivation). Keeping them separate is what stops architecture artefacts from blurring into one another.

• What — data and the things the enterprise manages
• How — functions and processes
• Where — locations and networks
• Who — people, roles and responsibilities
• When — timing, events and schedules
• Why — goals, strategy and motivation

Six rows: stakeholder perspectives

The rows represent perspectives — the different audiences who need a view of the enterprise. They run from the most abstract to the most concrete: the executive scope (the planner's view), the business model (the owner's view), the system model (the designer's view), the technology model (the builder's view), the detailed representations (the subcontractor's view) and finally the operating enterprise itself.

Each row is a legitimate, complete view in its own right, aimed at a real stakeholder. The value of the framework is that a cell — the intersection of one question and one perspective — is a single, primitive, non-redundant model. Thirty-six cells in total describe the enterprise without overlap.

How Zachman relates to TOGAF and ArchiMate

Because Zachman classifies rather than prescribes, it sits comfortably alongside method-based frameworks. TOGAF gives you the ADM — a process to run the work. ArchiMate gives you a notation to draw the artefacts. Zachman gives you a grid to check that the set of artefacts is complete and correctly placed.

In practice, teams use them together: run a TOGAF-style cycle, model the results in ArchiMate, and use the Zachman grid as a completeness check to confirm every question and every perspective has been addressed. They answer different questions, so they do not compete.

Using Zachman pragmatically with Archilu

Few organisations populate all thirty-six cells at once, and they should not try to. The pragmatic adoption is to use the grid as a thinking and review tool — pick the cells that matter for a given decision, and let the framework expose the gaps you have been ignoring, such as an undocumented motivation column or a missing 'Where'.

Archilu supports a Zachman-aligned practice by holding the business, application, data and technology descriptions as one connected, queryable model rather than scattered documents. Because the elements and their relationships are real objects, you can see where coverage is thin and where perspectives disagree. To find your starting point, Archilu's free EA maturity assessment scores ten dimensions and returns a prioritised plan in about ten minutes. The Zachman Framework is a trademark of Zachman International.

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

Practical checklist

Use this sequence to connect strategy to execution outcomes.

• Translate strategic goals into capability-level outcomes
• Map dependencies across business, app, data, and tech domains
• Define architecture decision checkpoints in roadmap cadence
• Track progress with measurable delivery and risk indicators