Benefits Realisation — From Business Case to Outcomes

The Benefits Gap

Research consistently shows that organisations focus on delivery metrics (on time, on budget, to scope) but neglect outcome metrics (did the investment deliver value?). A programme delivered on time but achieving only 20% of expected benefits is a failure — regardless of how well the delivery was managed.

Benefits realisation management ensures that the outcomes promised in the business case are planned for, tracked during delivery, and measured after go-live. It shifts the conversation from "did we build it?" to "did it work?"

The Benefits Lifecycle

1. Identification (Business Case Stage)

During business case development, identify and document expected benefits:

For each benefit, define:

• Description: What will improve? (Be specific — "improved efficiency" is not a benefit)
• Type: Financial (cost saving, revenue increase) or non-financial (speed, quality, satisfaction, compliance)
• Measure: How will we know it's been achieved? (Specific metric with current baseline and target)
• Baseline: Current performance level (measured, not estimated)
• Target: Expected performance after delivery (with timeframe)
• Owner: Who is accountable for realising this benefit? (A business stakeholder, not the PM)
• Dependencies: What must be true for this benefit to materialise? (Adoption, training, process change)

Example:

• Description: Reduce manual invoice processing time
• Type: Financial (cost saving)
• Measure: Average time per invoice (minutes)
• Baseline: 12 minutes per invoice (measured over Q1 2025)
• Target: 3 minutes per invoice (by Q3 2025, 6 months post-go-live)
• Owner: Head of Finance Operations
• Dependencies: Staff trained on new system, old process decommissioned, 80% adoption achieved

2. Planning (Programme Initiation)

Create a Benefits Realisation Plan that maps how delivery outputs lead to business outcomes:

The Benefits Map: Outputs → Outcomes → Benefits → Strategic Objectives

Example:

• Output: Automated invoice processing system deployed
• Outcome: Finance team processes invoices 4x faster
• Benefit: £200K annual cost saving (3 FTE redeployed)
• Strategic Objective: Reduce operational costs by 15%

The Measurement Plan:

• When will each benefit be measured? (3, 6, 12 months post-go-live)
• Who will measure it? (Benefits owner, not the programme team)
• What data source provides the measurement? (System reports, surveys, financial data)
• What's the minimum acceptable benefit level? (Below which the investment is considered unsuccessful)

3. Tracking (During Delivery)

Don't wait until go-live to think about benefits. Track leading indicators during delivery:

• Adoption readiness: Are users being trained? Is change management progressing?
• Process readiness: Are new processes designed and documented?
• Data readiness: Is the data needed for benefit measurement being captured?
• Stakeholder engagement: Are benefit owners engaged and prepared to measure?

Report benefits tracking in programme governance alongside delivery progress. If adoption readiness is low, the benefit won't materialise regardless of how well the system works.

4. Realisation (Post-Delivery)

After go-live, measure actual benefits against targets:

3-month review: Early indicators. Is adoption progressing? Are leading metrics moving in the right direction?

6-month review: Primary measurement point. Are quantified benefits being achieved? If not, what's preventing realisation?

12-month review: Full assessment. Final benefit measurement. Lessons learned. Decision on whether further investment is needed.

5. Sustaining

Benefits don't sustain themselves. Without active management:

• Users revert to old processes
• Workarounds emerge that bypass the new system
• Organisational changes erode the conditions that enabled the benefit
• New priorities divert attention from benefit-sustaining activities

The benefits owner is accountable for sustaining benefits beyond the programme's lifecycle.

Common Benefits Categories

Financial Benefits (Quantifiable)

• Cost reduction (headcount, infrastructure, vendor, process)
• Revenue increase (new products, improved conversion, expanded market)
• Cost avoidance (prevented future spend, regulatory fines avoided)
• Working capital improvement (faster invoicing, reduced inventory)

Non-Financial Benefits (Measurable but not in £)

• Speed (reduced cycle time, faster time-to-market, quicker customer response)
• Quality (fewer defects, higher customer satisfaction, reduced rework)
• Compliance (regulatory requirements met, audit findings resolved)
• Capability (new skills, new market access, improved decision-making)
• Risk reduction (single points of failure removed, disaster recovery improved)

Benefits Governance

Programme-Level

• Benefits tracker reviewed in every steering committee meeting
• Benefits owners attend steering quarterly to report on realisation progress
• Benefits at risk are escalated with the same urgency as delivery risks

Portfolio-Level

• Aggregate benefits across all programmes for executive reporting
• Compare actual benefits realised vs business case projections across the portfolio
• Use historical realisation rates to challenge future business cases (if programmes typically achieve 60% of projected benefits, factor that into investment decisions)

Measuring Benefits Realisation Effectiveness

• Benefits identification rate: % of programmes with clearly defined, measurable benefits at initiation. Target: 100%
• Benefits measurement rate: % of programmes that conduct post-delivery benefits reviews. Target: 100%
• Benefits realisation rate: Actual benefits achieved ÷ projected benefits. Target: >70%
• Time to benefit: Months from go-live to measurable benefit realisation. Track and benchmark.
• Benefits sustainability: Are benefits still being realised 12 months post-delivery? Target: >80%

Anti-Patterns

Vague benefits: "Improved efficiency" without a specific metric, baseline, or target. Fix: every benefit must be measurable with a defined baseline and target.

No benefits owner: The programme team "owns" benefits. After the programme closes, nobody measures them. Fix: assign a business stakeholder as benefits owner from day one.

Benefits theatre: Benefits are defined to justify the business case but nobody intends to measure them. Fix: make benefits measurement a condition of programme closure sign-off.

Delivery-only focus: Programme governance tracks delivery metrics obsessively but never discusses benefits. Fix: include benefits status in every steering committee agenda.

---

Download the [Benefits Realisation Tracker template](/templates) to track financial and non-financial benefits from business case to realisation.