Most transformation budgets get approved for the wrong reasons.
The business case was compelling. The vendor demo was impressive. The timeline looked achievable. The board said yes.
Eighteen months later, the program is over budget, behind schedule, and the executive sponsor is explaining to the same board why the promised ROI has not materialized.
The approval process failed — not because the decision-makers were uninformed, but because they asked the wrong questions.
After three decades of leading enterprise transformations for Fortune 500 organizations, I have sat in hundreds of budget approval meetings. The programs that succeed almost always begin with a different kind of conversation than the ones that struggle. Here are the six questions that separate them.
1. How will we measure whether this delivered value — before we spend the first dollar?
This is the most important question and the one most frequently skipped. Organizations routinely approve transformation investments based on projected benefits without defining how those benefits will be measured. The result: a completed program with no mechanism to prove what it delivered.
Benefits realization is not a post-program activity. It is a design decision made at the start. If your business case cannot answer "how will we measure benefit X by date Y using metric Z," the benefit should not be in the business case.
2. Who owns each promised benefit?
A benefit without an owner is a projection, not a commitment. Every line item in your business case representing a dollar of value should have a named individual who is accountable for delivering it. Not a team. Not a department. A person.
When benefit ownership is diffuse, accountability disappears. When accountability disappears, measurement stops. When measurement stops, value evaporates — quietly and without anyone being responsible.
3. What is our governance model for program-level decisions?
The question is not whether you have governance. Every program has governance in some form. The question is whether your governance is designed to make decisions at the speed your program requires.
Ask specifically: what is the maximum time allowed for an unresolved decision before it escalates? If your answer is "it depends" or "we'll figure it out," your governance is not designed — it is improvised. Improvised governance produces two-week problems that become six-week delays.
4. What is our data readiness baseline?
Data migration is the silent killer of enterprise transformation. It is consistently underestimated, consistently underfunded, and consistently responsible for go-live failures that nobody predicted — except anyone who has done this before.
Before approving a transformation budget, you should know: what is the current state of our master data? Who owns data quality decisions? What does "clean enough to go live" mean, and who signs off on it?
If your team cannot answer these questions in the budget approval meeting, your data workstream needs investment before your technology workstream begins.
5. What is our change management plan, and is it adequately funded?
Change management is the first thing cut when budgets get tight and the first thing blamed when programs fail. The pattern is so consistent it has become a cliché — and yet organizations keep repeating it.
A reasonable benchmark: change management should represent 15–20% of total program budget for large-scale transformations. If your budget allocates 5%, you are not managing change. You are hoping for it.
6. What does failure look like, and what is our contingency plan?
This question makes sponsors uncomfortable, which is exactly why it is valuable. Programs that never discuss failure scenarios are programs that encounter failure without preparation.
Asking this question does not invite failure. It surfaces the assumptions buried in your business case and forces an honest conversation about risk tolerance, contingency funding, and program recovery options.
The organizations that beat the 65% failure rate are not luckier or better resourced than the ones that struggle. They ask harder questions before they start.
Rick Catalano is the creator of the AMIGA Framework and author of The AI Project Manager. Download the free Governance Framework Template at theaiprojectmanager.ai