Approval is a decision to invest. It is not proof that the promised value will arrive.
The business case is impressive. There are projected cost reductions, productivity improvements, better service, perhaps a new technology platform. Finance reviews the assumptions. Leadership approves the investment. The project gets a sponsor and a delivery team.
Then attention shifts to schedule, scope, milestones, and risk.
All of those deserve management. But a curious thing can happen: the person responsible for delivering the project becomes far easier to identify than the person responsible for delivering the benefit.
A project manager can tell you whether the implementation is on track. Who can tell you whether the business has changed in the way required to make the financial model true?
Benefits do not appear on their own
Consider an investment justified by reduced processing costs. The new system works. Staff have been trained. Yet the organization keeps the old approval process, maintains duplicate reporting, and preserves the same staffing and resource allocation assumptions.
The software may have been delivered correctly. The savings are still trapped in the operating model.
That is not necessarily a project management failure. It may be a failure to make the business decisions the investment depended on.
A more useful business case
At approval, leadership should be able to name four things:
- The business outcome: What will improve, and what is the baseline?
- The operating change: Which work, decisions, behaviors, or responsibilities must be different?
- The benefit owner: Who remains accountable once the implementation team has finished?
- The verification point: When and how will the organization determine whether value actually appeared?
These answers won't guarantee success. But their absence is a warning worth taking seriously.
Keep the investment under management after launch
A disciplined post-launch review shouldn't be a victory lap or a hunt for somebody to blame. It should identify which assumptions held, which didn't, what operating obstacles remain, and what leaders need to decide next.
Projects need delivery accountability. Investments need business accountability. Confusing the two is an expensive habit.
Peloton perspective: If your business cases routinely promise improvements that don't appear in operating results, examine who owns the changes required to realize them—not just who delivered the technology.