Before I would back a benefits forecast, I want to know whether the business can take the actions it depends on.

That means looking across the portfolio. Several sensible business cases may need the same service leaders, technology team or supplier. A cost reduction may depend on another change being completed first. Those constraints belong in the forecast.

Find the operating action behind the number

For each material benefit, ask what has to change in the business. If a cost is coming out, identify the expenditure and the decision that removes it. If capacity is increasing, establish where that capacity will be useful. If revenue is expected to grow, explain how the operating change enables the additional business.

A supplier negotiation, team consolidation or withdrawal of an old service cannot remain an assumed consequence of a technology milestone. It needs an owner, a place in the plan and a realistic decision date.

Make the competing demands visible

I would bring the shared resources and dependencies together before accepting each workstream’s delivery dates. Who is needed by several initiatives? Which teams are also absorbing changes to their day-to-day service? Where is one forecast relying on another initiative’s result?

The largest business case will not necessarily be the first piece of work to do. A smaller change may release a constraint that several others depend on. Equally, delaying one initiative may put a material benefit at risk.

The executive team needs those consequences to make the choice. A list of competing priorities leaves the people doing the work to resolve it themselves.

Show what supports the benefit forecast

An opportunity, an approved plan, an implemented change and a realised benefit are different positions. Reporting needs to preserve the distinction.

Finance and the operating owner should agree the baseline, action, timing and evidence for each material benefit. If a supplier decision or resource assumption is unresolved, that uncertainty needs to remain visible in the forecast.

The service also has to be able to carry the change. A cost reduction that depends on sustained overtime, unresolved control weaknesses or temporary support needs further examination.

Put the decision in front of the executive team

I want the review to end with a clear recommendation: which work should continue, what needs to be sequenced differently, where additional capacity is justified and which assumption needs testing before a commitment is made.

That gives the Board a basis for judging the route to the financial result. It also gives delivery teams a plan they can work to, with the important choices made by the people authorised to make them.

Related experience

Connecting operating redesign to delivery

Read the anonymised case