Enterprise Intelligence

So, Approve construction (implementation) decisions if you want. But do not call them architecture. Architecture must outlive the architect. If it does not, it was never architecture.

Level 1 remains inside IT. Business departments are still external at this stage. That is why Level 1, even when strong, is not enterprise anatomy yet—it is IT anatomy convergence.

Most Enterprise Architecture “maturity models” measure capability. They describe whether an organisation has EA activities, governance forums, standards, repositories, tooling, and whether those activities appear more consistent over time. This is a useful lens for assessing the presence of EA practice. But it is not the lens ICMG Enterprise Anatomy™ uses. The ICMG Enterprise Anatomy™ model does not measure how mature your EA practice looks . It measures something else entire

Enterprise Architecture maturity is therefore not the progression of IT governance practices or tools. It is the elevation from isolated architectural activity toward explicit enterprise anatomy governing decisions across the organization.

In practice, architecture compliance often means one thing: the IT project is using an approved vendor, platform, or technology stack. This is not architecture. It is procurement control.

Organisations believe they are enforcing architecture — when they are only enforcing vendor and tool uniformity.

And so, like 1820 medicine, they certify surface practices — but lack anatomy understanding.

This isn’t Enterprise Architecture for a Bank. This is an IT roadmap, wearing a borrowed title. If 12 of the 15 critical banking functions were never touched, it’s not EA. It’s IT transformation mislabelled as Enterprise Architecture

This “Enterprise Architecture” covered perhaps 2–3 of the airline’s 15 core departments – maybe ~20% of the enterprise – leaving the other ~80% of the organization unmapped and unmanaged by any unified architecture.

Across the Middle East, “Enterprise Architecture” has become a brand — a badge claimed by banks, airlines, ministries, telecom giants, and consulting firms alike. But behind the banners and certifications, a pattern reveals itself.

Across the Middle East, everyone says they’ve “implemented EA.” → A national airline. → A major Gulf bank. → A digital authority in the region. → A global logistics player based in the UAE. → Even a ministry that awarded EA certifications. But when we looked under the hood? What we found wasn’t ENTERPRISE ARCHITECTURE.

Naming parts doesn’t create function. You can agree on terminology—and still build disconnected systems.

Until the foundation is correct, speed is irrelevant. Because scaling confusion only guarantees faster failure.

Human anatomy doesn't change depending on the hospital or doctor. Yet in EA, everyone thinks they're allowed their own interpretation.

Let’s clearly understand why genuine Enterprise Architecture must structurally represent all 14 clearly defined departments,

How many CEOs actively use TOGAF to drive strategic business decisions? 0%.

If you asked successful CEOs whether they actively involve TOGAF-certified architects in enterprise-wide strategic planning, market expansio

TOGAF architects "enable" integration within IT systems, but they rarely lead real strategic integration across finance, operations, or hr

Calling everything outside IT, "the business" isn't just linguistic—it reveals a deep structural misunderstanding at the core of frameworks

When you dive deeper into what TOGAF certification really covers, a troubling fact emerges: these professionals are trained narrowly in IT

If you ask the same CEOs how often they consult TOGAF-certified architects for strategic decisions, the answer is likely: "Rarely, if ever."

Curiously, the majority of CFOs, COOs, and HR leaders have little to no interaction with TOGAF-certified professionals.

If Enterprise Architecture is genuinely about the enterprise—then why does it report primarily to CIOs and not CEOs?