Yagnesh RamalingamWhen the forecast became a political artefact
Forecast cycle time dropped from 18 days to 6, because the argument about last month’s actuals stopped happening twice.
The headline number
18→6 days
Monthly forecast cycle
Pattern and numbers from an operating role I held before Zerentro, anonymised. Not a Zerentro client engagement.
The result
The numbers that moved.
- 18→6 days
Monthly forecast cycle
Source · FP&A calendar at the time, anonymised
- 1 actuals source
Finance and ops reconciled to a single close number
Source · Month-end pack
The story
How it got fixed. In four parts.
Situation, complication, intervention and result. This is one company. The general case is the framework.
Read the frameworkEvidence for: Extended Planning & Analysis (XP&A) · Governed data · Decision latency
Situation
The monthly forecast was a two-and-a-half-week ritual. Ops and finance arrived with different ‘actuals’ for the prior period. Half the cycle was spent reconciling the past, not planning the next one.
Complication
XP&A had been framed as a tooling upgrade — a planning platform on top of the same contested numbers. The platform did what platforms do: it made the disagreement faster and more widely distributed.
Intervention
I treated actuals as a governed object first. One close number, one owner, one window in which it can change. Planning inherited that number; it was no longer allowed to negotiate it. The planning platform stayed. The contract underneath it changed.
Result
The forecast cycle compressed because the first week of argument disappeared. Leadership still disagreed about the future — that is the job. They no longer disagreed about last month.
Common questions
Why did the forecast cycle take 18 days?
Ops and finance arrived with different actuals for the prior period, so half the cycle was spent reconciling the past instead of planning the next one.
Did the planning platform change?
No. The platform stayed. The contract underneath it changed: one close number, one owner, and one window in which it can change.
Is this a Zerentro client engagement?
No. It is a pattern, with its numbers, from an operating role held before Zerentro, anonymised.
Work with me
Monday looks like this? Bring the number.
A free 30-minute call with Yagnesh. You'll find out if the problem is the data, the definition or who owns it.