A business case is a measurement plan, not a one-off pitch
The technology business case that secures board approval and the technology business case that actually guides decision-making during and after delivery are rarely the same document. The approval document is built to persuade. The measurement plan (which tells you whether the investment is producing the return it promised) is usually an afterthought, and often nonexistent.
This is a structural problem with how organisations evaluate technology investments, and it is one that costs organisations significantly, both in direct waste and in the lost opportunity to learn what is and is not working.
The approval-measurement gap
Business cases are evaluated at a single point in time: the investment decision. Once approved, the case is filed and the delivery programme begins. The projections that justified the investment (the productivity gains, the cost reductions, the revenue enablement) become background context rather than active management targets.
At go-live, the programme closes. The benefits that justified the investment transfer to operational owners who were not part of the business case conversation, are not measured against the projections, and have no structural reason to track whether the case was right.
The result is that organisations make investment decisions based on business cases that are never validated, cannot learn from their assumptions, and cannot improve over time. The organisation that approved ten technology investments over five years and has no systematic view of which delivered their projected returns is the norm, not the exception.
What a measurement plan actually requires
Baseline metrics before you start. You cannot measure improvement without a baseline. This sounds obvious. It is consistently skipped. The baseline data should be collected and validated before the technology programme begins. Not reconstructed from memory at the post-implementation review.
Named benefits owners with delivery accountability. Every benefit projection in a business case should have a named owner: someone whose role includes tracking and reporting on that specific benefit for a defined period after go-live. Without this, benefits belong to nobody.
Measurement intervals, not just targets. A target for year three is not a measurement plan. A measurement plan includes checkpoints at six months, twelve months, and twenty-four months, with clear criteria for what good looks like at each stage and a defined process for acting on the data.
An honest assumptions log. Every business case is built on assumptions. The measurement plan should explicitly record those assumptions so that, when reality diverges from the model, you can understand why, and apply that learning to the next case.
The shift in mindset
A business case is not a document that gets written before the investment and filed afterwards. It is the beginning of a measurement commitment that runs for the life of the benefit it projected. Treat it that way, and your investment decisions improve. Treat it as a one-off pitch, and you are perpetually flying blind.