Deloitte Delivered EA for Transformation. Why Can’t the CEO Trace Strategy to Operations?

The issue is not whether Deloitte delivered EA. The issue is whether that EA helps the CEO trace one real business decision from strategy to operations.

Many large enterprises and government institutions have worked with Deloitte or similar consulting firms on Enterprise Architecture, transformation, operating model, technology modernization, governance, digital programs, and architecture capability building.

The work may have produced serious deliverables.

EA framework. Governance model. Architecture principles. Capability maps. Application views. Technology views. Roadmaps. Operating model recommendations. Transformation workstreams. Architecture review structures. Platform modernization plans. Implementation guidance.

The CIO may have received useful visibility.

IT applications may be mapped. Technology standards may be clearer. Architecture governance may be stronger. Roadmaps may be structured. Modernization priorities may be visible. Delivery programs may be better governed.

But the CEO has a different question.

1. Can this EA show how one real business decision moves from strategy to operations?

2. Can it show where value is created, protected, delayed, or leaked?

3. Can it show which departments carry the decision?

4. Can it show which process, system/sub-system logic, component specifications, implementation tasks, and operations are affected?

If not, the EA may have helped the CIO. But it has not yet become visible enough for the CEO. That is the gap.

Most EA was delivered for the CIO

This is not a criticism of Deloitte. Deloitte and similar firms often deliver what they were asked to deliver. Many EA programs are sponsored through the CIO organization. So the work naturally focuses on the CIO’s needs:

IT portfolio visibility. Application rationalization. Technology modernization. Architecture governance. Cloud migration. Platform delivery. Cyber and risk alignment. Solution review. Data and integration architecture. Digital transformation support.

These are useful.

But CIO-focused EA is not the same as CEO-level Enterprise Anatomy.

The CIO may need to know:

Which systems exist? Which platforms are duplicated? Which applications should be rationalized? Which technologies should be standardized? Which projects need architecture review? Which roadmap should IT follow?

The CEO needs to know something different:

Which business decision creates value? Which department owns the outcome? Where does the decision move? Where does it slow down? Where does value leak? Which operational dependency is hidden? Which strategy cannot be executed because the enterprise anatomy is not visible?

That is why EA delivered for the CIO may still not answer the CEO’s question.

The CEO does not need another EA artifact

A CEO does not wake up asking for another capability map.

The CEO asks:

Why is execution slow? Why does a small policy change take weeks? Why do departments interpret the same strategy differently? Why does transformation value disappear between the business case and operations?

Why does IT say the system is ready while operations says the process is broken?

Why does a cost reduction in one department create risk or revenue leakage somewhere else?

Why do we still need meetings, memory, vendor explanations, and old project files to understand impact?

These are not technology questions alone. They are enterprise anatomy questions.

If EA cannot answer them, then the CEO may respect the EA investment but still not use it every day.

The issue is not whether the EA exists. The issue is whether the CEO can see the decision trace.

Decision trace is the missing bridge

Take one real business decision.

A pricing change. A funding approval. A customer onboarding rule. A risk threshold. A regulatory reporting change. A product launch. A subsidy eligibility rule. A service-level commitment. A disbursement trigger. A cost-reduction decision.

Now ask:

1. Can this decision be traced from strategy to operations?

2. Can leadership see the intended value outcome?

3. Can process owners see the activity sequence?

4. Can business and IT teams see the systems and sub-system logic?

5. Can component owners see the forms, rules, workflows, datasets, reports, screens, APIs, policy clauses, contracts, or configurations that carry the decision?

6. Can delivery teams see the human and IT tasks required to change it?

7. Can operations teams see what must be monitored, supported, corrected, and maintained every day?

If not, the EA may be complete as a consulting deliverable. But it is not yet usable as CEO-level decision visibility.

P1 Strategy is only one perspective

A common mistake is to treat strategy as something above the enterprise.

Strategy is defined. Then operating model is designed. Then initiatives are created. Then governance is installed. Then execution is monitored. Then KPIs are tracked.

This sequence looks logical.

But it creates a separation between strategy and the enterprise body that must execute it. In ICMG Enterprise Anatomy™, P1 Strategy is one of the six perspectives of ICMG Enterprise Anatomy™.

It gives direction and value outcomes.

But it becomes meaningful only when connected to:

P2 Process — the activity sequences through which the department realizes the strategy element.

P3 Systems / Logic — the business system and sub-system logic that governs how the department works. This includes policy logic, rule logic, decision logic, workflow logic, data logic, timing logic, approval logic, exception logic, people coordination logic, partner logic, and where relevant, IT system logic.

P4 Component Specifications — the concrete components that carry or express that logic. These may include forms, templates, role definitions, policy clauses, approval matrices, service rules, operating checklists, reports, dashboards, datasets, screens, APIs, workflows, configurations, training material, contracts, or physical/digital assets.

P5 Implementation Tasks — the work required to create, change, deploy, or improve those components. This includes human tasks within the department and IT tasks supporting that department.

P6 Operations — the daily business operations and IT operations required to run, monitor, support, correct, and maintain the department’s work.

This is where Deloitte-delivered EA often needs elevation. The artifacts may exist.

But the trace from P1 to P6 may still be incomplete.

Why CIO-focused EA still falls short for the CIO

Most EA delivered for the CIO is assumed to be useful because it improves IT visibility.

But the problem is deeper.

Much of the current EA evidence is actually P5-heavy: implementation artifacts, solution designs, system views, integration diagrams, application maps, roadmaps, standards, and project documentation.

The CIO, however, carries a major P6 responsibility: keeping services running, monitored, supported, secured, maintained, and continuously improved.

That means the CIO needs more than P5 artifacts.

The CIO needs to understand the P1–P4 trace behind what is being operated:

P1 Strategy — why this capability or service exists.

P2 Process — which business activity sequence it supports.

P3 Systems / Logic — which business, rule, data, workflow, timing, approval, exception, and IT logic governs it.

P4 Component Specifications — which business and technical components carry that logic.

Without P1–P4, the CIO is operating systems without full anatomy. Even the CIO is often asked to operate P6 with mostly P5 evidence and weak P1–P4 visibility. That is why EA must be elevated into ICMG Enterprise Anatomy™.

One CEO decision moves across many departments

A CEO decision rarely stays inside IT.

1. A revenue decision may move across product, pricing, marketing, sales, channels, customer experience, billing, risk, partners, operations, data, and IT.

   
   

2. A cost decision may move across procurement, finance, HR, vendors, legal, operations, service levels, contracts, systems, and support.

   
   

3. A regulatory decision may move across compliance, legal, process owners, reporting, audit, data, operations, vendors, and IT.

   
   

4. A customer experience decision may move across product, service, support, digital channels, complaints, CRM, analytics, billing, operations, and finance.

So the decision must be traced across the enterprise functions where it actually moves. That is why ICMG Enterprise Anatomy™ uses the D1–D15 × P1–P6 view.

1. D1–D15 represent the major enterprise functions or departments.

2. P1–P6 represent the six perspectives from strategy to operations.

Together, they create a 90-cell anatomy view. This is not more documentation.

It is a way to see whether the enterprise can make, change, execute, and monitor decisions without depending on memory.

Why Deloitte EA may need elevation

Deloitte may have delivered useful EA work.

The governance model may be useful. The operating model may be useful. The capability maps may be useful. The technology views may be useful. The roadmaps may be useful. The transformation workstreams may be useful. The modernization plans may be useful. The platform architecture may be useful. The implementation documents may be useful.

But each artifact must be tested against one question:

Can this help the CEO trace one real business decision from strategy to operations?

If yes, it becomes part of the elevated anatomy.

If no, it remains an EA artifact — useful for the CIO, but not sufficient for CEO-level decision visibility.

That is the difference between CIO-focused EA and ICMG Enterprise Anatomy™.

The real value gap

This is not about whether the EA engagement cost $1M, $3M, or $5M. The bigger issue is the value gap it leaves behind.

If the CEO cannot see the decision trace, then the enterprise may still lose value through:

slow change impact analysis, duplicated transformation work, misaligned departments, unclear rule ownership, delayed implementation, hidden operational risk, vendor dependency, manual interpretation, incorrect prioritization, missed revenue, unprotected margin, poor customer experience, or regulatory exposure.

So the issue is not the EA spend. The issue is whether the EA investment became usable for decisions worth $50M, $100M, or $300M.

That is the CEO gap.

How ICMG elevates Deloitte-delivered EA

ICMG does not ask the enterprise to throw away what Deloitte delivered.

The right move is not to restart EA. The right move is to elevate it.

ICMG examines the existing EA work and asks:

What was delivered? What can be reused? Which artifacts support decision traceability? Which artifacts remain CIO-focused? Where does the trace break? Which P1–P6 perspectives are weak? Which departments are outside the trace? Which parts still depend on meetings, memory, spreadsheets, vendor explanations, or personal interpretation?

Then ICMG selects one real business decision and traces it across:

P1 Strategy, P2 Process, P3 Systems / Logic, P4 Component Specifications, P5 Implementation Tasks, P6 Operations.

Then the trace is extended across the relevant D1–D15 enterprise functions. The result is not another EA report. The result is a visible enterprise decision trace.

The board-level question

For a board, CEO, ministry, CIO, CFO, COO, or transformation leader, the question is not:

Did Deloitte deliver EA?

The better question is:

1. Was the EA delivered only for CIO visibility, or can the CEO now see the decision trace?

2. Can the CEO trace one strategy into process, systems/logic, component specifications, implementation tasks, and operations?

3. Can the CEO see which departments carry the decision?

4. Can the CEO see where value is created, protected, delayed, or leaked?

5. Can the CEO see where execution depends on memory?

If not, the EA may have been delivered. But it has not yet become ICMG Enterprise Anatomy™.

Diagnostic Question

If Deloitte delivered your EA for the CIO, can your CEO now trace one real business decision from strategy to operations across the departments where that decision actually moves?

Can the CEO see the process, system/sub-system logic, component specifications, implementation tasks, and operations that create, protect, delay, or leak value?

If not, the EA may be complete as a CIO-facing deliverable. But the CEO still cannot see the decision trace.