Every programme has a benefits case. Very few of them are tracked after approval. The business case gets filed, the programme delivers its outputs, and the question of whether any actual value was created gets quietly dropped. Nobody asks because nobody set up the infrastructure to answer it.
I've reviewed programme closures where benefits were declared achieved because the system went live on time. The system going live is not a benefit. It's a precondition. The benefit is what changes in the business as a result. That distinction is the difference between a programme that delivered and a programme that appeared to deliver.
Benefits realisation isn't a reporting exercise. It's the mechanism that connects programme investment to organisational value. Without it, you're measuring the wrong things.
Why Benefits Cases Fall Apart After Approval
The failure is almost always structural, not intentional. Three patterns repeat consistently.
Benefits are owned by the programme, not the business. When the programme team is accountable for benefits, those benefits disappear when the programme closes. Benefits need to be owned by named business leaders who remain in post after go-live and are accountable for the outcomes in their area.
There is no baseline. You cannot measure improvement without knowing where you started. Programmes that fail to capture baseline metrics before delivery begins have no objective way to demonstrate value post go-live. Baselines captured after go-live are almost always influenced by what the team wants to show.
Benefits are defined as outputs, not outcomes. "Implement a new CRM system" is an output. "Increase sales conversion rate by 12% within 12 months of go-live" is an outcome. Business cases full of output-based benefits are impossible to realise because they describe activities, not value.
How to Build a Framework That Actually Works
A benefits realisation framework doesn't need to be complex. It needs three things: ownership, measurement, and a review cadence that outlasts the programme.
Step 1: Define benefits in outcome terms at business case stage. Every benefit should answer: what will be measurably different in the business, by how much, and by when? If a benefit can't be expressed in those terms, it's not a benefit. It's an aspiration.
Step 2: Assign a named benefit owner before approval. Every benefit needs a named individual, not a team or a function, who is accountable for its realisation. That person's name goes into the business case. They sign off on the baseline. They report on progress at 3, 6, and 12 months post go-live.
Step 3: Capture baselines before delivery begins. For every quantifiable benefit, measure the current state before the programme changes anything. Processing time, error rates, cost per transaction, customer satisfaction scores. Whatever the benefit is measuring, baseline it now.
Step 4: Build post go-live reviews into the programme schedule. Before the programme closes, schedule three review points: 3 months, 6 months, and 12 months post go-live. These reviews are not optional. They are part of the programme's accountability structure. The benefit owners present to the original programme sponsor.
Step 5: Connect benefits to the PMO's reporting. Benefits realisation should appear on the PMO's portfolio dashboard alongside delivery metrics. If the PMO is tracking schedule and budget but not benefits, it's measuring activity, not value.
| Review Point | What to Measure | Who Presents |
|---|---|---|
| 3 months post go-live | Adoption rates, early usage indicators | Benefit owners |
| 6 months post go-live | Initial benefit indicators, variance from baseline | Benefit owners + PMO |
| 12 months post go-live | Full benefit assessment against business case | Benefit owners to sponsor |
According to PMI's benefits realisation research, organisations with mature benefits realisation practices are 72% more likely to meet their programme objectives. The investment in the framework is small. The cost of not having it is the entire programme.
The Benefits Realisation Mindset Shift
The shift that makes benefits realisation work isn't a process change. It's a mindset change. Programmes need to stop treating go-live as the finish line. Go-live is when the real work begins.
The organisations that do this well treat the programme director as accountable for benefits realisation until the 12-month review, not just until go-live. That single change in accountability structure transforms how programmes are designed, delivered, and closed.
If your PMO doesn't have a benefits realisation framework, the programmes you're delivering are generating outputs, not outcomes. Our team can help you build a framework that survives programme closure and delivers accountability at board level. Book a 30-minute discovery call.