Find the constraint. Reset the route forward.

A ten-working-day diagnostic for CIOs, CTOs and Transformation Directors who need a clearer basis for technology, architecture and delivery decisions.

When to use the Scan

Use when

A major programme is delayed

Dependencies are unresolved or decisions are repeatedly reopened.

Use when

Leadership needs independent evidence

A platform, cloud, data or operating model investment needs challenge before commitment.

Use when

Governance is creating friction

Architecture assurance is slow, inconsistent or being bypassed by delivery teams.

Use when

The estate is opaque

Technology visibility is too weak to manage risk, duplication or cost confidently.

Use when

A new leader needs a baseline

A rapid, evidence-led view is needed before priorities are reset.

Use when

Activity lacks coherence

There is movement, but not enough ownership, sequencing or shared direction.

What we examine

Strategic clarity

Are technology choices linked to business priorities, investment decisions and transformation outcomes?

Strategy, portfolio, roadmap and governance evidence.

Weakness creates investment uncertainty and competing priorities.

Decision governance

Are material decisions owned, made at the right level and resolved quickly enough?

Decision forums, thresholds, logs and escalation paths.

Weakness causes reopened decisions and avoidable delay.

Delivery flow

Where are dependencies, late decisions, assurance bottlenecks and rework slowing delivery?

Programme plans, dependency maps, risk logs and delivery forums.

Weakness reduces momentum and creates hidden rework.

Estate health

Where are duplication, fragility, debt, integration risks, data issues or avoidable cost accumulating?

Estate views, platform inventories and risk evidence.

Weakness increases operational exposure and cost.

Architecture operating model

Does architecture have the mandate, engagement model and working rhythm needed to influence outcomes?

Role definitions, forums, artefacts and engagement patterns.

Weakness makes architecture advisory rather than decisive.

How the Scan runs

Day 1: scope the business question and evidence request. Days 2 to 4: review existing materials. Days 3 to 6: executive and delivery interviews. Days 6 to 8: synthesis, scoring and prioritisation. Days 9 to 10: executive report and leadership read-out.

What you receive

Five-lens assessment and heatmap. Top findings with evidence and business impact. Delivery drag map. Decision-rights recommendation. Estate exposure view for the selected problem. 30-60-90 day action plan. Leadership decisions required.

What it is not

Not a long maturity assessment. Not a new architecture repository. Not a generic strategy exercise. Not a slide-heavy review with no owner or next step. Not an attempt to document every system in the organisation.

Engagement options without a sales agenda

Architecture Recovery Session, Architecture Recovery Scan, Architecture Reset and Fractional Chief Architect support are only recommended when there is a clear, owned intervention to undertake.