Value Tracking
Value Tracking After Go-Live Is Where Programs Quietly Die
By Ashutosh Bansal·March 19, 2026
The value case dies between quarter two and quarter four post go-live. Always. Here is the structural fix.
The value case dies between quarter two and quarter four post go-live. Always. I have watched this cycle so many times across so many enterprises that I now treat it as the central design problem of the run phase, not a quality-of-life concern.
The pattern is predictable. The program ships. The first quarterly readout shows a modest lift — partial, because the platform has only been live for ninety days, but directionally consistent with the value case. The second readout shows more lift, on a wider scope. The third readout is “in progress.” The fourth readout — if it happens at all — has been rolled into a broader business performance review, where the platform’s contribution can no longer be isolated. By the sixth quarter, no one is tracking the value at all. The platform is running. The value, theoretically, is being delivered. No one can prove it.
This is not malice and it is not laziness. It is a structural defect in how value tracking is set up. The value case lives in a slide deck owned by the program manager. The program manager rolled off at go-live. The slide deck was handed to operations. Operations does not have the time or the analytical depth to recompute the value case quarterly. The CFO does not have the trust in the methodology to defend it without the program manager in the room. So it quietly stops.
The fix is structural. Value tracking has to be instrumented inside the platform, not in a parallel BI report. It has to be owned by the Decision COE, not by the program manager. It has to publish on cadence, with the same discipline the controller publishes a P&L.
Three rules we apply, without exception, on every Run engagement we operate.
01Value tracking is a platform capability, not a deliverable.
The metrics, the comparisons, the policy attribution — all of it lives inside the platform’s value accounting module. The numbers are auto-computed. The methodology is versioned. The CFO does not need the program manager in the room.
02The Decision Value Statement publishes monthly.
It looks like a P&L. It states: this quarter, the platform delivered this lift, attributed to these decisions, governed by these policies, against this baseline. The CFO signs off. The board sees the same statement quarterly.
03The Decision COE chairs the methodology.
When the methodology needs to change — because the business changed, because the policy changed, because the scope expanded — the change is documented, the prior period is restated, and the audit trail is preserved.
This is not exotic work. It is accounting discipline applied to decisions. The reason it does not happen in most enterprises is that nobody installed it. Once installed, it runs.
The platform that cannot defend its own value, six quarters in, will not be there in eight.
More from Insights
Data & Integration
The Data Layer Is the Implementation
Half of every decision intelligence program is data work. The other half is decisions. Ordering them in the wrong sequence is why most programs slip.
March 6, 2026·A GitaCloud Principal
Change & Adoption
Adoption Is Not Training. Adoption Is Operating Model.
The two-week training course at the end of an implementation is the most expensive mistake in enterprise software. We retired it. Here is what we do instead.
February 22, 2026·A GitaCloud Principal