Most boards do not approve transformation budgets.

They approve assumptions that have never been tested.

No sensible person would agree to a fixed price on a house before the architect has drawn the plans. Before the soil conditions are understood. Before the structural requirements are known. Before anyone has counted the trades, the materials, the dependencies, or the hundred variables that determine what the work actually costs. A number produced before that understanding exists is not a budget. It is a guess with a signature on it.

The question worth sitting with is how many of the assumptions inside your transformation budget were tested before the board approved it. Not validated by the vendor proposing the work. Actually tested, against your data, your processes, your people, your systems, and your operational reality.

In most cases the answer is: fewer than the board realized at the time.

The Governance Condition

The budget is constructed from untested assumptions, using industry benchmarks, systems integrator estimates, and experience from programs that may or may not resemble the one being approved. Systems integrator estimates are produced in good faith and reflect delivery experience. They are not independent assessments of the organization’s specific readiness.

In one multi-country retail transformation, the implementation budget was based on a vendor estimate that assumed clean, structured data across all entities. The data assessment conducted six weeks after contract signature revealed that two of the four entities had data quality issues requiring between eight and fourteen months of remediation. The original estimate had allocated ten weeks for data migration. The total program cost increased by 34 percent.

In a global manufacturing rollout covering twelve sites, the go-live date was communicated to the board before discovery was complete. By the time discovery revealed the true complexity of the integration layer, the date had appeared in two investor communications and one regulatory filing. The program accommodated the date. The quality of what was delivered to it was not what would have been delivered to a later one.

In one PE-backed industrial transformation, a new CFO arrived at month eight. Their first question: had the approved budget been independently stress-tested against the actual program scope? It had not. The question opened a budget conversation that would have been less expensive at month two.

Most transformation budgets are not exceeded. They are corrected.

This distinction matters. Exceeded implies something went wrong in delivery. Corrected implies the original number was based on incomplete information and the delivery process produced the information required to establish a more accurate one.

Governance Pattern: The Assumption Budget

Observed when:

  • The budget was produced before a detailed assessment of data quality, process maturity, or integration complexity was conducted
  • The estimate was based primarily on vendor benchmarks or industry comparisons rather than organization-specific discovery
  • Significant scope, effort, or complexity emerged during delivery that was not visible at the point of approval
  • The budget revision is described internally as an overrun when it is more accurately a correction
  • The program is managing to the original budget through scope reduction, quality compromise, or timeline extension that has not been formally approved

Commercial consequence:

Budget revisions treated as delivery failures rather than discovery corrections, creating accountability consequences for people not responsible for the original estimate. The most damaging budget surprises arrive late, when options for managing them are fewest.

If This Feels Familiar
  • The original budget was approved before detailed discovery of data quality, process complexity, or integration scope.
  • The budget is described internally as under pressure but that pressure is not being formally reported to the board.
  • There is internal awareness that the approved number is no longer the right number, but no formal mechanism to revise it.
  • The program is managing to the original budget through adjustments that have not been formally approved.

Board Questions

1.Which assumptions inside this budget have actually been tested against organizational reality? Which have not?
2.What did the discovery process reveal about the assumptions the budget was built on? Has that been formally reported to the board?
3.Is the program being managed to the approved budget through scope reduction or quality compromise not formally approved?
4.If the original budget is wrong, what is the actual cost of what is being delivered? Who is responsible for producing that number?
5.Is there an independent source that can tell the board the difference between what was approved and what is actually being delivered?

Governance Intervention

Business Case Assurance. Independent review of the business case before commitment, examining which assumptions have been tested and which have not.

Transformation Alignment and Readiness Review. A structured examination that tests the assumptions the budget was built on: data quality, process maturity, business readiness, internal capacity.

TRC Solutions provides independent governance for SAP and ERP transformation programs. The Governance Engine is the institutional framework through which TRC carries that accountability.