Transition Architecture

Intro

A transition architecture formally describes an intermediate state on the path from the baseline to the target architecture. Multiple transitions may map the time‑phased progression.

Key points:

• Provides realistic steps to manage risk and value.
• Aligns funding and delivery with milestones.
• Common use cases across EA/BPM/Data/App/Tech include staged decommissioning, phased migrations, and capability uplifts.
• Pitfall: skipping transitions, leading to big‑bang risk and disruption.

Examples:

• Interim data platform coexisting with legacy warehouses.
• Phased rollout of an integration layer by domain.
• Temporary process variants during system cutover.

In practice:

Define each transition with scope, dependencies, risks, and KPIs; connect to the roadmap.

Related terms: Baseline; Target Architecture; Roadmap

FAQs:

Q: How many transition states are ideal?
A: As few as needed to reduce risk and deliver value.

Q: Who approves transitions?
A: Architecture governance with portfolio oversight.

‍