Waymark & Cairn

Approach

A planned path from current state to target state to future state

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

  • Where are we today, and what does it cost us?
  • What should the technology look like to meet our strategy?
  • In what order do we change it without stopping the business?

Six steps across three states

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

Discover

Interview stakeholders, read strategy and budget documents, and agree the scope, constraints and success measures.

Output: scope statement, stakeholder map

Step 2 · Current state

Baseline

Inventory capabilities, applications, data stores, integrations, infrastructure and controls, with owners, cost and risk.

Output: baseline architecture, risk register

Step 3 · Target state

Design the target

Set principles and design reference architectures across business, data, application, technology and security.

Output: target architecture, decision records

Step 4 · Target state

Analyze the gaps

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

Plan the transitions

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

Govern and adapt

Review designs against standards, record exceptions and update the roadmap as strategy and technology change.

Output: review cadence, living repository

Change in stages that keep the business running

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

Systems as they run today

Changes: nothing yet.

Stays stable: everything, now documented, owned and measured.

Transition 1

Foundations

Changes: identity, network, data standards and landing zone are put in place.

Stays stable: existing systems keep serving customers.

Transition 2

Migration

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

Operating to standard

Changes: legacy is retired and operations follow the agreed standards.

Stays stable: governance keeps the architecture current.

Principles I design by

Business first

Every technology choice traces back to a capability or outcome the business has named.

Simple over clever

Fewer moving parts are easier to run, secure and hand over. Complexity needs a reason on record.

Designed for failure

Recovery targets, fallbacks and monitoring are part of the first design, not added after an outage.

Secure by default

Identity, encryption and segmentation are standard patterns that new systems inherit.

Reuse before build

Existing platforms and managed services come first, so effort goes to what differentiates you.

Decisions on record

Significant choices are written down with context and alternatives, so they can be revisited.

What you keep

Everything is delivered in formats your team can open, edit and extend, held in a repository you own.

  • Capability map
  • Application and data inventory
  • Target reference architectures
  • Architecture decision records
  • Phased roadmap
  • Data dictionary and models
  • Infrastructure-as-code repository
  • Runbooks and recovery plans

Start with a baseline

A current-state assessment is the quickest way to see where you are and what to do first.

Book a discovery call