ETEGY / Transformation / Key Concepts / Actual-state discovery
Key Concept 06 · Research-based read

You cannot transform a model you have only assumed. Start from its actual state.

Most programs begin from a current-state slide — an idealized diagram of how work is supposed to run. The actual state is different, and it is where the transformation requirements actually live.

What "actual-state discovery" means

Actual-state discovery is reading how the operating model really runs today — the true intake, the side doors, the handoffs, the rework — before any future state is drawn. It is not a maturity survey or a reference process map; it is the system as it actually behaves.

Deloitte's own transformation practice front-loads exactly this: a repeatable read that documents and assesses current-state processes, then runs a gap analysis between the as-is and the to-be. The read comes first.

Activity is everywhere. The disciplined read is rare.

Organizations are pouring money and motion into transformation — while almost none have the maturity to ground it in a real read of the system.

6%

of organizations qualify as transformation-maturity "leaders" — even as 74% plan to increase transformation investment.

Forrester · 2026
73%

say they cannot even define the metrics to measure a transformation's value — because the baseline was never established.

Deloitte
Transformation activity vs. readiness
Increasing transformation investmentForrester, 2026
74%
Can't define metrics to measure valueDeloitte
73%
Running 4+ initiatives a yearForrester
72%
Qualify as transformation leadersForrester
6%
Forrester (2026) and Deloitte. The money and the motion are everywhere; the disciplined read of the actual state is the 6%.

Forrester's read is that most still treat transformation as disconnected projects — spend and motion without a grounded read of the system they are changing.

Current-state is not actual-state

A current-state diagram describes how work is meant to run. The actual state is how it runs when no one is drawing it — and the difference is precisely where the transformation requirements hide.

Deloitte's finding on measurement is the tell: 73% cannot define the impact metrics, with "inability to collect data" and organizational silos close behind. You cannot measure value you never baselined against the real system.

What only the actual-state read surfaces

These are the things a reference process map cannot show — and the things a transformation has to be scoped around:

  1. The side doorsHow demand really enters, around the official front door
    Intake
  2. The handoff failuresWhere work stalls in the seams between functions
    Seams
  3. The rework loopsEffort spent redoing what a broken step produced
    Rework
  4. The blind spotsOutcomes no dashboard is actually watching
    Proof
  5. The requirementsWhat the model must do to carry strategy to a provable result
    Requirements

How ETEGY reads it

The actual state is not a preliminary step to skip under time pressure — it is where the real transformation requirements are found. We begin there by design.

The ETEGY read

We open every engagement with a Zero-Based read of the operating model's actual state, structured across the GSDPI lifecycle — surfacing the pains, gains, and requirements a current-state slide can't show. See the ZBT Discovery →

Design from the slide and you automate the fiction. Start from the actual state.