The forecast moved again. The board wants to know why, finance wants to know what changed, and the programme explains itself in a language that connects to neither. The variance is real, but its causes live in operational reality: a supplier extended, a parallel capability kept alive, a handover that has not started.
The CFO is asked to defend a number whose foundations belong to other functions.
A financial report shows the variance. It does not show that the delay scenario extends because operational independence is not yet demonstrated, or that a parallel-operation cost continues precisely because a technical dependency remains unresolved.
When the operational assumptions are invisible, every conversation about the number becomes a negotiation about credibility.
- Financial consequence connected to the enterprise events and assumptions that produced it.
- Composition kept explicit: what is accrued, what is forecast variance, what is scenario. Numerator, denominator and time horizon stay visible.
- The assumptions that would change the number, named as conditions rather than buried in a footnote.
Exposure with an inspectable basis, and the confidence that the arithmetic will survive the room.
The cost of the current operating reality, read against the commitment rather than against last quarter.
Which financial assumptions are conditions on the decision, and what would move them.
The number stops arriving alone. It arrives with its basis, its assumptions and its conditions, and the discussion moves from defending the figure to deciding upon it.
Defend the number and understand what would change it.
Desired outcomeWhat this position looks like on paper: the Project Umber Executive Decision Brief →