Target Architecture — IT definition

Target architecture is the projected vision of the IT estate at a 3 to 5 year horizon: target application portfolio, target infrastructure, structuring technology choices, urbanization principles. It contrasts with current architecture (the IT estate as it is today) and transition architecture (intermediate states).

It is one of the central deliverables of any enterprise architecture or IT urbanization practice. It translates corporate strategy into a technical target enforceable against projects, and provides the frame within which daily arbitration (buying a new application, cloud migration, modernizing a legacy) must fit.

Why a target architecture

Without an explicit target, every project recreates its own implicit vision — leading to a patchwork IT estate of conflicting local choices. Target architecture brings:

• •Consistency: new projects align with a common direction.
• •Enforceability: a project deviating from the target must justify the gap in an architecture committee.
• •Trajectory: the target lets you plan transformation programs in milestones.
• •C-suite communication: simple visualization of "where we are heading", readable by business directions.
• •Budget arbitration: prioritize investments that move closer to the target.

Contents of a target architecture

A documented target architecture typically covers several views aligned with TOGAF:

### Target business architecture

• •Priority business capabilities.
• •Target operating model (centralized / decentralized / federated).
• •Key business processes and their digitalization principles.

### Target application architecture

• •Target application portfolio (apps kept, replaced, retired).
• •Functional mapping of target application blocks.
• •Integration principles (API-first, event-driven, ESB or iPaaS).
• •Structuring choices (single ERP vs best-of-breed, SaaS-first, cloud-native).

### Target data architecture

• •Single sources of truth (customers, products, employees).
• •Target data platform (data lake, data warehouse, lakehouse).
• •Data governance.

### Target technology architecture

• •Cloud strategy (mono-cloud, multi-cloud, hybrid, sovereign).
• •Target infrastructure (Kubernetes, serverless, reduced on-premise).
• •Security (Zero Trust, IAM, generalized SSO).

### Target security architecture

• •Zero Trust principles.
• •Perimeters and trust zones.
• •Authentication standards (SSO, systematic MFA).
• •Regulatory compliance (DORA, NIS2, GDPR, ISO 42001).

Target architecture and trajectory

The target only makes sense with a documented trajectory: the path from current to target, in annual milestones. The trajectory identifies:

• •Projects: to launch each year.
• •Applications to decommission: progressively.
• •Dependencies: between programs.
• •Transition risks: (service continuity, temporary dual-run).

Without trajectory, the target stays a beautiful drawing without operational impact.

Target vs transition architecture

A major transformation (cloud migration, ERP refresh, M&A) often imposes a transition architecture: an intermediate state that may last 2 to 5 years, where old and new coexist. Well documented, transition architecture avoids the legacy becoming the new default by absence of a clear cutover milestone.

Building the target architecture

Typical 3 to 9 month roadmap:

1. Strategic vision: collect C-suite and business orientations (business priorities, M&A, regulatory constraints).
2. Current state: current application mapping, technical debt audit, cost analysis.
3. Urbanization principles: 10-15 golden rules to guide evolution.
4. Target per layer: application, data, technology, security.
5. Trajectory: 3-year milestone roadmap.
6. Validation: architecture committee, C-suite.
7. Communication: posters, dashboards, documentation accessible to projects.
8. Annual update: the target evolves with strategy.

Target architecture and governance platform

A theoretical target architecture is useless if not continuously confronted with IT estate reality. Kabeen provides continuous visualization of the gap between target and current: off-target applications, obsolete technologies, non-compliant dependencies, delayed programs. This confrontation turns target architecture from an annual deliverable into a daily steering tool.