Your EA Consulting Partner Finished the Work. How Do You Elevate It into ICMG Enterprise Anatomy™?

The answer is not to discard the EA work already delivered. The answer is to test whether it can be elevated into something business leaders use every day.

Many organizations have already invested in Enterprise Architecture consulting. The work may have been delivered by PwC, Deloitte, EY, KPMG, Accenture, Infosys, Wipro, CTS, or another consulting or technology partner.

The output may include frameworks, governance models, principles, standards, roadmaps, capability maps, application views, technology views, platform architectures, integration views, repository structures, maturity reports, and implementation documents.

Some of this work may be useful.

Some of it may be reusable.

Some of it may already contain important architecture evidence.

So the right question is not:

Should we restart EA?

The better question is:

How do we elevate what already exists into ICMG Enterprise Anatomy™?

That is where the real work begins.

Step 1: Separate EA artifacts from decision use

The first step is to separate two things.

One is the EA artifact. The other is the business decision it should support.

A framework may exist. A governance model may exist. A roadmap may exist. A repository may exist. A platform architecture may exist. A maturity report may exist. An implementation document may exist.

But can these artifacts help a business leader make or change one real decision?

Can they help answer:

Which strategy does this decision support? Which process executes it? Which rules, data, UI, timing, workflow, and integration logic enforce it? Which APIs, screens, datasets, reports, workflows, and configurations carry it? Which implementation tasks changed it?Which operations must monitor it?

If not, the artifact may still be useful.

But it has not yet become part of the enterprise’s daily decision system.

Step 2: Select one real decision

ICMG Enterprise Anatomy™ elevation does not begin with abstract EA language.

It begins with one real enterprise decision.

For example:

A pricing change. A funding approval. A credit risk threshold. A customer onboarding rule. A disbursement trigger. A regulatory reporting change. A service eligibility rule. A network outage compensation decision. A crew disruption recovery decision. A patient pathway update .A policy change. A product launch decision.

This decision becomes the test.

If one real decision cannot be traced clearly, then the existing EA work has not yet become daily decision visibility system.

Step 3: Trace the decision across P1–P6

The selected decision is then examined across the six ICMG Enterprise Anatomy™ perspectives.

P1 Strategy is the direction and value outcomes the enterprise wants to achieve.

P2 Process is the sequence of activities required to realize the strategy.

P3 Systems / Logic is the systems and sub-system logic that execute or enforce the business flow, including rules, data, function, UI, timing, workflow, and integration logic.

P4 Component Specifications are the data structures, APIs, screens, reports, workflows, rules, configurations, and components where the logic is instantiated.

P5 Implementation Tasks are the build, configure, modify, test, deploy, and change activities performed by people and IT teams.

P6 Operations are the business and IT operations that run, monitor, support, and maintain the service.

This trace shows whether the EA work is connected from intent to execution. In many organizations, P5 evidence is strong.

There are implementation plans, delivery documents, project files, sprint backlogs, solution designs, platform diagrams, API documents, deployment records, and test evidence.

Some P6 evidence may also exist.

But P1, P2, P3, and P4 are often scattered, weak, hidden inside documents, or dependent on people’s memory. That is where the trace breaks.

Step 4: Extend the trace across D1–D15

A real decision does not stay inside IT. It moves across enterprise functions.

1. A funding decision may move across strategy, investment origination, evaluation, risk, legal, finance, disbursement, portfolio monitoring, and impact tracking.

2. A pricing decision may move across product, sales, finance, risk, channels, customer experience, billing, operations, and IT.

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

4. A customer onboarding rule may move across sales, compliance, risk, digital channels, identity systems, CRM, data, support, and operations.

That is why ICMG Enterprise Anatomy™ examines the decision across D1–D15 × P1–P6.

1. D1–D15 represent the enterprise departments or functions where decisions actually move.

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

Together, they create a 90-cell anatomy view.

This view shows which parts of the existing EA work are usable, which parts are missing, and where the enterprise still depends on meetings, memory, spreadsheets, vendors, or personal interpretation.

Step 5: Identify what can be reused

Elevation does not mean throwing away what was delivered. The existing EA work may contain useful material.

The governance model may be reusable. The principles may be reusable. The capability maps may be reusable .The application views may be reusable .The technology standards may be reusable. The roadmaps may be reusable .The repository structure may be reusable. The platform diagrams may be reusable. The integration views may be reusable. The implementation documents may be reusable .The maturity report may be reusable.

But reuse cannot be assumed.

Each artifact must be tested against one question:

Does this help trace a real decision from strategy to operations?

If yes, it becomes part of the elevated anatomy.

If no, it remains an EA artifact — possibly useful, but not sufficient for daily decision-making.

Step 6: Create the missing anatomy evidence

Once the trace breaks are visible, the next step is to create the missing evidence.

This may require clarifying the P1 strategic intent.

1. It may require defining the P2 process sequence.

2. It may require exposing the P3 systems and sub-system logic.

3. It may require identifying the P4 component specifications.

4. It may require connecting the P5 implementation tasks.

5. It may require mapping the P6 operational responsibilities.

6. It may also require connecting the decision across the relevant D1–D15 enterprise functions.

This is where elevation becomes real. The organization is no longer debating EA in abstract terms. It is creating the missing anatomy required for daily decision-making.

Step 7: Create a visible ICMG Enterprise Anatomy™ prototype

For many organizations, the first practical output should be one strong prototype.

Not the entire enterprise. Not every department. Not every system.

One selected decision. One visible trace. One clear demonstration of how the decision moves across P1–P6 and across the relevant enterprise functions.

This prototype helps leadership see the difference between delivered EA artifacts and usable Enterprise Anatomy.

1. 
   

2. It shows where the existing EA work helps.

3. It shows where it fails.

4. It shows what must be created.

5. It shows how EA can become something business leaders use every day.

Step 8: Synchronize department-wise anatomy

A decision trace is not complete until the departments see the same decision.

If finance sees one version of the decision, operations sees another, IT sees another, and the vendor sees another, then the enterprise is still fragmented.

ICMG Enterprise Anatomy™ elevation synchronizes the anatomy across departments.

The question becomes:

Are departments using the same decision trace? Are rules consistent across functions?Are system and sub-system logic interactions visible? Are component specifications traceable? Are implementation tasks connected to business intent? Are operations monitoring the right outcome?

This is where EA starts becoming a shared enterprise asset.

1. Not just a document.

2. Not just a repository.

3. Not just a governance structure.

A daily decision system.

Step 9: Update and maintain the anatomy

Enterprise Anatomy is not created once and frozen.

It must be maintained.

Strategies change. Policies change. Products change. Processes change. Rules change. Systems change. APIs change. Screens change. Reports change. Data structures change. Vendors change. Operations change.

Each change can affect the anatomy.

So ICMG Enterprise Anatomy™ must be updated as the enterprise changes. Without update and maintenance, the enterprise slowly returns to memory.

That is why the elevation journey includes anatomy synchronization, update, and maintenance.

Step 10: Rate and certify the achieved maturity level

Only after the anatomy evidence exists should certification be considered. ICMG Enterprise Anatomy™ certification should not be treated as a badge attached to generic EA language.

It should be based on visible evidence.

The question is:

1. What maturity level has actually been achieved?

2. Has the organization only created EA practice maturity?

3. Has it created one IT anatomy?

4. Has it created one department anatomy?

5. Has it connected multiple departments?

6. Has it created variable-rich anatomy that can support scenario analysis, change impact, and predictive decision evaluation?

That is why ICMG Enterprise Anatomy™ maturity is different. It does not only ask whether the EA function is mature. It asks whether the enterprise itself is visible, traceable, usable, and maintainable.

What leadership receives

The output of EA elevation is not another generic EA report.

Leadership receives clarity on:

What already exists. What can be reused. Where the decision trace breaks. Which P1–P6 layers are weak. Which departments are outside the trace. Which value outcomes are not visible. Which platform evidence is mainly implementation-heavy. Which parts still depend on meetings, memory, spreadsheets, vendors, or personal interpretation. What must be created before EA can become daily decision infrastructure. What maturity level can be certified. What must be updated and maintained going forward.

That is the practical value of elevation.

The board-level question

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

Did our EA consulting partner finish the work?

The better question is:

Can we elevate that work into something business leaders use every day to trace decisions, assess change impact, see value, guide implementation, and monitor operations?

If the answer is no, the organization does not need another abstract EA discussion.

It needs to know exactly where the trace breaks, what can be reused, what must be created, and how the anatomy will be maintained. That is the role of ICMG Enterprise Anatomy™.

Diagnostic Question

If your EA consulting partner finished the work, what is the next step?

Can the delivered EA be elevated into a working decision trace across strategy, process, systems/logic, component specifications, implementation tasks, and operations — across the departments where the decision actually moves?

Can that trace be synchronized, updated, maintained, and eventually certified as ICMG Enterprise Anatomy™?

If yes, the EA investment can become a daily decision system. If not, the work may be complete as an EA engagement.

But it has not yet become Enterprise Anatomy.