Transformation spends the money. Realizing the value is a different discipline — and most never build it.

What "value realization" actually means

Value realization is the discipline of proving that a transformation's intended benefit actually arrived — not that the project shipped. KPMG's framing is the useful one: successful transformations prioritize value and align every initiative to measurable outcomes. Value is captured, not assumed.

The distinction matters because most programs are governed on scope, schedule, and cost — the things a PMO can see — while the benefit itself goes unmeasured, and quietly unrealized.

The gap between spend and captured value

The money moves. The value, reliably, does not — and executives say so themselves.

KPMG names the mechanism plainly: value leaks across a transformation unless it is actively managed — which is why their own corrective begins by reviewing past programs to find where the benefit went.

What gets counted instead of value

Programs report what is easy to see: milestones hit, systems live, training delivered. PwC's read is direct — most transformations fail to deliver full value, losing impact in the space between strategy and execution. A completed milestone is not a captured benefit.

KPMG's corrective is telling: they review past programs specifically to find where value leakage occurred — an admission that, by default, no one was watching the benefit at all.

Where value leaks — point by point

Value rarely disappears in one place. It drains through a series of gaps, each one small enough to ignore until the benefit is gone:

1. Benefit never baselinedNo starting number, so there is nothing to prove movement against
   Baseline
2. Value assumed at approval, never re-testedThe business case is filed at sign-off and never revisited
   Business case
3. Measured by delivery, not outcomeScope, schedule, and cost stand in for whether value arrived
   Delivery
4. No owner of the benefitThe PMO owns the plan; no one owns the result
   Ownership
5. Value leaks across the seamsCaptured in one function, lost in the handoffs between them
   Leakage

How ETEGY reads it

Every leak above traces to the same absence: the value was never made provable. We fix that at the front end — a baseline you can transform against, and a standard that ties a reported result back to the work that produced it.