The Business Case That Wins Funding Is Often the One That Sinks Delivery

There is a moment early in most large programs that decides more than anyone admits. It is the moment the business case gets written to win funding.

To secure approval, benefits get pushed up and timelines get pulled in. The people writing the case know how the committee thinks. Bigger returns and faster delivery clear the bar. Modest, honest numbers get sent back for more work. So the document that goes into the funding meeting is optimized for one thing: getting a yes.

That is understandable. It is also the root of a problem that surfaces a year later.

The sales tool becomes the scorecard

Once the money is approved, the business case does not get filed away. It becomes the baseline. Every steering committee, every status report, every executive check-in measures the program against the numbers that were written to impress, not the numbers anyone believed.

The benefits case assumed full adoption on a schedule that ignored how people actually change. The timeline assumed a clean run with no integration surprises, no vendor delays, no competing priorities pulling your best people away. None of that holds. It never does.

So a program doing genuinely good work starts looking like it is behind. The gap between the promise and the reality grows, and the team gets pulled into defending it.

What the gap does to a team

When a program is judged against numbers no one could hit, the behavior changes in predictable ways.

Status reporting turns into narrative management. Leads spend their week explaining variance instead of solving the actual delivery problem. Honesty gets punished, because whoever surfaces bad news first owns it. So the news gets softened, and by the time reality is undeniable, the room for a graceful correction is gone.

The worst part is what it does to the people who have to live with the change. Transformation lands when someone changes how they work on a Tuesday morning. That adoption curve is real and it takes time. When the business case pretends adoption is instant, the whole program is set up to blame the users for a schedule that was never realistic.

Honesty is not sandbagging

The answer is not to pad every estimate and protect yourself with slack. That is its own kind of dishonesty, and experienced committees see through it.

The answer is to write the case around when value actually shows up. That means being specific about sequencing and about the human side of the change.

Tie benefits to adoption, not go-live

A system going live does not produce a benefit. People using it differently produces the benefit. Map the benefit to the behavior change that creates it, and put a realistic curve on that behavior change. If a process improvement depends on three thousand people working a new way, say how long that takes and what has to happen for it to stick.

Separate the funding number from the delivery baseline

If the political reality of your organization demands an ambitious headline to get funded, then be explicit that the delivery plan carries its own baseline with its own assumptions. Do not let the approval number silently become the measure of success. Name the difference in the open, with the sponsor, before delivery starts.

Build the governance to hold the truth

A business case that survives contact with reality needs governance that can absorb bad news without punishing the messenger. That means a steering group that reviews assumptions, not just variance, and a sponsor who will re-baseline when the facts change rather than demanding the team hit a number that stopped being real six months ago.

Fix the case, or inherit the blame

Most delivery failures I get called into are not delivery failures at all. The work is competent. The problem was set at funding, when the case was written to sell rather than to guide, and no one went back to reconcile the two.

If you are running a program right now, the useful question is not whether you are on track. It is whether the track you are being measured against was ever honest. If it was not, the time to renegotiate that with your sponsor is now, while there is still room to do it calmly.

The people doing the work deserve to be judged against reality. So does the program.