From Spend to Substance: Building a Value Realization Function That Earns Its Seat
Photo: Press Service of the President of the Republic of Azerbaijan, CC BY 4.0, via Wikimedia Commons
A transformation program is approved with a business case projecting forty million dollars in annual benefit. Twenty-two months later, the program closes on schedule, the project management office issues a completion report with green indicators, and every milestone is documented. What no one can state with confidence is whether the forty million arrived — or where it went.
Finance holds the invoice. The PMO holds the plan. Neither holds the outcome. That void between approved spend and realized business result is where enterprise value quietly evaporates, and it is the specific gap a value realization function exists to close.
The Structural Blind Spot
Traditional governance divides labor sensibly: the PMO manages scope, schedule, and delivery quality; finance manages budget and capitalization; business units manage operations. Each discipline is well served. The benefit itself belongs to none of them.
This is not a failure of diligence; it is a failure of assignment. A PMO measured on on-time delivery will optimize for on-time delivery. A business unit leader absorbed in daily operations will treat a transformation program's benefits as someone else's forecast. And a finance organization tracking capitalization rules has no mandate to chase operational behavior change six months after go-live. The result is a systematic pattern in which spend is verified and value is assumed.
What a Value Realization Function Actually Does
A value realization office is not a benefit-tracking dashboard. It is a small, senior function with four concrete responsibilities.
Establishing honest baselines. Before an initiative launches, the function documents the current-state metric — cost per transaction, cycle time, attrition rate, whatever the benefit depends on — using the same measurement method that will be used after implementation. Baselines set retroactively are the single most common mechanism for manufacturing success.
Mapping benefit ownership. Every dollar of projected benefit is assigned to a named operational owner with the authority to change the process that produces it. Benefits without an owner are forecasts, not commitments.
Tracking the runway, not the launch. Most benefit erosion occurs in the twelve to eighteen months after go-live, when adoption decays, workarounds harden, and the original process discipline loosens. The function monitors that runway and reports on it to the executive committee.
Triggering course correction. This is the responsibility that distinguishes the function from reporting. When a benefit line is tracking below threshold, the office has standing to escalate and, where necessary, to recommend suspension of further spend. Without that authority, it becomes an observer.
Where It Should Sit
Placement matters more than headcount. The function must report to a level with enterprise-wide authority — typically the CFO, the COO, or a transformation executive reporting to the chief executive — and it must be structurally independent of the programs it evaluates. A value office embedded inside the transformation program it monitors will produce favorable findings with impressive consistency.
Equally important, it should not absorb the PMO. Delivery management and value assurance are different disciplines, and combining them invites the same conflict of interest that arises when an auditor also runs the department being audited.
Standing One Up in Ninety Days
A pragmatic sequence works better than a comprehensive design.
Days 1 to 30: inventory. Select the ten to fifteen largest active initiatives and reconstruct, for each, the approved benefit, the baseline, the named owner, and the current measurement. The exercise usually reveals that a third of the benefits are unmeasurable as defined.
Days 31 to 60: define the measurement line. Agree with finance on a single set of benefit definitions so that the value office and the financial reporting system produce reconcilable numbers. Divergent definitions destroy credibility faster than missed targets.
Days 61 to 90: establish the review cadence. A monthly operational review with benefit owners and a quarterly executive review with funding consequences. The first quarterly review should present one honest negative finding; an office that reports only good news in its first cycle will never be trusted with anything else.
Interfaces That Determine Credibility
With finance, the relationship should be one of reconciliation, not subordination — the value office uses the same general ledger discipline but interprets it against operational metrics. With the PMO, the interface is handoff: the PMO owns delivery to go-live, the value office owns the runway afterward, and both report into a single portfolio view. With business units, the relationship must be collaborative rather than investigative, since benefit owners are the people who must actually change how work gets done. With internal audit, a light coordination touch prevents duplicated assurance effort and conflicting findings.
Measuring the Office Itself
A value realization function should be held to three metrics: the percentage of active initiatives with a validated baseline and named owner; the accuracy of benefit forecasts at twelve months post-implementation; and the dollar value of spend redirected or stopped as a result of its findings. That last number is the one that earns the seat at the table.
Enterprises do not lack ambition in transformation. They lack the institutional machinery to confirm whether the ambition paid. Building that machinery is less expensive than the alternative — continuing to approve large programs on the strength of a business case no one is accountable for delivering.