The Ten Elements of an Enterprise Architecture

Why ten, and why together

These are the elements that, in combination, determine what an enterprise can execute. Individually they are all familiar; most leadership teams have worked on several of them. The failure mode is almost never ignorance of an element. It is treating each one as a separate project with its own owner, timeline, and definition of success.

Architecture is the opposite of that. The elements are interdependent by construction: decision rights are meaningless without cadence, cadence produces nothing without a plan, a plan cannot be executed by leaders who have not been built for the authority it requires. Improve one in isolation and the others pull the result back.

Ten elements of one architecture. They are designed together because they only hold together.

01–03: Intent, simplification, and leadership

Strategic intent — what the enterprise is actually trying to become, stated precisely enough to be designed against. Vague intent is the most expensive document in a business, because every downstream element inherits its ambiguity.

Front-to-back 80/20 simplification — complexity removed end to end, so capacity and margin move to where value is genuinely created. Simplification precedes structure. Designing an organization around complexity you intend to remove locks the complexity in.

Leadership architecture — the roles, altitudes, and capabilities the strategy demands, built ahead of need rather than discovered during a crisis. This is the work of LEAD — Develop Capability & Drive Results — and it is where coaching belongs: as a component that develops leaders able to operate the architecture, never as the product itself.

04–06: Governance, planning, and cadence

Organizational structure and governance — a vertical authority stack of ownership, board, executive, and operating layers, with explicit boundaries at each altitude. Most governance dysfunction is not misconduct; it is two altitudes trying to make the same decision.

Annual operating plans — strategy converted into a funded, sequenced, owned plan rather than an aspiration. If the plan does not name who, by when, funded how, it is a forecast of intentions.

Operating cadence — the quarterly, monthly, weekly, and daily rhythms that carry decisions and evidence at the right frequency. Cadence is the heartbeat of the architecture; it is also the element most often mistaken for a meeting schedule.

07–08: Decision rights and reinforcement

Decision rights and accountability — who decides, who is consulted, who executes, designed and documented rather than negotiated case by case. Ambiguity here is the single most reliable source of executive friction, and the cheapest to remove.

Performance management and executive incentives — measures and rewards aligned to the architecture, so the designed behavior is also the rational behavior. When incentives contradict the design, the incentives win and the design is blamed.

09–10: Enablement and renewal

ERP and CRM as enterprise enablers — systems configured to serve the management system, not selected in the hope that software will create discipline. Technology does not create transformation; leadership does. A well-implemented system on a poorly designed architecture simply makes the wrong behavior faster and better documented.

Continuous learning through ARC™ — Assess, Refine, Commit — the renewal engine that runs across the whole architecture and keeps it current as conditions change. Accountability for it lives in the operating rhythm, not in a separate step. Without it, every architecture becomes a period piece, perfectly suited to a business that no longer exists.

How to read your own gaps

The useful diagnostic is not which elements are strong. It is which are strong in isolation. An excellent plan with no cadence, precise decision rights with contradicting incentives, a capable executive team inside an undefined governance boundary — these are the patterns that explain why capable organizations underperform their own strategy.

The remedy is sequencing, not simultaneity. Intent and simplification first, because they set the load the rest of the structure must carry. Then structure, governance, and decision rights. Then plan, cadence, and reinforcement. Then renewal, permanently.

A ten-element self-read

• Intent: precise enough to design against, or merely agreeable?
• Simplification: actively removed front to back, or only ever added?
• Leadership: capability built ahead of the authority required?
• Governance: boundaries explicit at each altitude?
• Plan: funded, sequenced, and owned?
• Cadence: decisions closed, not just reviewed?
• Decision rights: documented and held?
• Incentives: reinforcing the design or fighting it?
• Systems: serving the management system or substituting for it?
• Renewal: a standing discipline or a periodic crisis?

Ten elements, one architecture. The enterprises that outperform are rarely better at any single element — they are the ones where all ten were designed to hold together.

A whole-system reading: the ten architected elements cut across every part of the operating system.