Approach
The method is the same on every engagement. It gives the business a documented baseline, a design it can fund and a staged route that keeps operations stable while the change happens.
Questions this answers
Each step produces something your team keeps. The colors mark the state: slate for current, teal for target, brass for future.
Step 1 · Current state
Interview stakeholders, read strategy and budget documents, and agree the scope, constraints and success measures.
Output: scope statement, stakeholder map
Step 2 · Current state
Inventory capabilities, applications, data stores, integrations, infrastructure and controls, with owners, cost and risk.
Output: baseline architecture, risk register
Step 3 · Target state
Set principles and design reference architectures across business, data, application, technology and security.
Output: target architecture, decision records
Step 4 · Target state
Compare baseline and target in each domain, then rank gaps by business impact, risk and effort.
Output: gap analysis, options with trade-offs
Step 5 · Future state
Group the work into stages that each leave a stable architecture, with dependencies, funding and owners.
Output: phased roadmap, transition architectures
Step 6 · Future state
Review designs against standards, record exceptions and update the roadmap as strategy and technology change.
Output: review cadence, living repository
Each transition architecture is a working state in its own right. The stages below show a typical shape; yours are set from the baseline and the roadmap.
Baseline
Changes: nothing yet.
Stays stable: everything, now documented, owned and measured.
Transition 1
Changes: identity, network, data standards and landing zone are put in place.
Stays stable: existing systems keep serving customers.
Transition 2
Changes: priority workloads and data domains move to the new standards.
Stays stable: old and new run side by side with a tested fallback.
Target
Changes: legacy is retired and operations follow the agreed standards.
Stays stable: governance keeps the architecture current.
Every technology choice traces back to a capability or outcome the business has named.
Fewer moving parts are easier to run, secure and hand over. Complexity needs a reason on record.
Recovery targets, fallbacks and monitoring are part of the first design, not added after an outage.
Identity, encryption and segmentation are standard patterns that new systems inherit.
Existing platforms and managed services come first, so effort goes to what differentiates you.
Significant choices are written down with context and alternatives, so they can be revisited.
Everything is delivered in formats your team can open, edit and extend, held in a repository you own.
A current-state assessment is the quickest way to see where you are and what to do first.