Capability
Advisory & enterprise architecture
Make the current estate understandable and turn modernization choices into an executable portfolio and transition roadmap.
Page purpose
What the Advisory & enterprise architecture capability delivers and how it connects to the modernization lifecycle.
Enterprise architecture is useful when it turns an incomplete estate into decisions that leaders can fund, sequence and govern. The work connects operating capabilities, applications, information, technology, ownership and change constraints rather than producing a target-state diagram in isolation.
The engagement establishes evidence for each portfolio disposition, defines viable transition states and makes assumptions, dependencies and residual risks reviewable. Recommendations remain vendor-neutral until requirements and decision criteria justify a narrower choice.
When to use this capability
Situations that call for this delivery capability.
- Application inventories list products but do not show business criticality, dependencies, lifecycle exposure or accountable ownership.
- Competing initiatives claim urgency without a common method for comparing value, risk, readiness and transition effort.
- Target architectures describe an end state while leaving coexistence, sequencing, funding boundaries and operational continuity unresolved.
Service scope
Outputs a buyer can inspect.
- Current-state capability, application, data and dependency views with confidence levels and evidence sources.
- Portfolio disposition register recording criteria, rationale, constraints, owners and unresolved questions.
- Target and transition architecture pack covering business, application, data, integration, platform and security concerns.
- Modernization wave plan with prerequisites, decision gates, indicative scope boundaries and governance responsibilities.
Delivery pattern
From discovery to acceptance evidence.
- Frame the decisions, stakeholders, scope boundaries and evidence standard before collecting architecture detail.
- Test documented views through interviews, system evidence and dependency tracing, marking uncertainty rather than hiding it.
- Compare options against agreed value, risk, cost, time, reversibility and operating-model criteria.
- Design transition states and portfolio waves, then review them with business, engineering, security, finance and operations owners.
Operating value
The operating change that should remain.
- A shared current-state model that exposes material gaps, dependencies and disputed assumptions.
- Defensible retain, retire, replace, rehost, replatform, refactor or rearchitect decisions at an appropriate level of granularity.
- A sequenced portfolio roadmap with decision gates, transition states, ownership and evidence required before further commitment.
Performance evidence
Evidence of impact, not activity completion.
- Percentage of in-scope systems with validated ownership, criticality and material dependencies.
- Percentage of proposed investments supported by an approved disposition and recorded decision rationale.
- Number and age of unresolved architecture decisions, assumptions and cross-wave dependencies.
Delivery boundaries
Boundaries that keep delivery honest.
- An inventory exercise can create apparent precision while critical dependencies and shadow systems remain undiscovered.
- A preferred platform or procurement outcome can bias dispositions before decision criteria are agreed.
- A roadmap can become obsolete if ownership, funding assumptions and review triggers are not maintained.
Decision questions
Questions that bound the capability before engagement.
Does enterprise architecture mean selecting a standard platform?
Platform selection is one possible downstream decision. The engagement first establishes operating need, estate evidence and decision criteria, which may support preserving, simplifying, retiring or introducing technology.
How detailed should the current-state assessment be?
Detailed enough to support the decisions in scope. Critical dependencies and high-risk assumptions need stronger evidence, while low-impact areas can remain at portfolio level.
Related decision