The Programme Is Green. Is the Investment Delivering?

I would expect an executive performance review to connect progress, expenditure and operating results. Otherwise, leadership can approve the next phase without seeing the cost or conditions of making the previous one work.

A completed project can leave an unfinished transition

Consider a hypothetical workflow programme. The platform launches on schedule, training is complete and implementation expenditure remains within budget. The delivery report is green.

Employees nevertheless continue using spreadsheets to handle exceptions. Managers maintain parallel approvals because nobody has agreed who can authorise the new process. Support teams absorb additional work, while the expected reduction in processing time remains unproven.

The implementation may have met its agreed scope. The business transition is still incomplete, and its remaining cost needs an owner.

Before funding another release, I would want to understand what prevents the organisation from retiring the previous way of working. That answer could change the investment priority.

Five dimensions should inform the same decision

I would build a short executive performance view around five connected questions.

Value: what has improved? Start with the intended business outcome and a credible baseline. A shorter processing time, fewer manual interventions or lower operating cost can demonstrate progress when the measure reflects the work actually being performed. Logins and training attendance provide useful context, but cannot establish the benefit alone.

Delivery: is the remaining plan credible? Examine critical milestones, unresolved dependencies and changes in the forecast. A completed technical task may depend on business approval or operational preparation before it contributes to a usable service.

Finance: what will it cost to finish and operate? Include expenditure incurred, contractual commitments, remaining work and the cost of transition. Spending below budget can conceal deferred work or costs transferred to another department.

Operation: can the business run it? Check service ownership, support, exception handling and recovery arrangements. A quiet incident report offers limited reassurance if the service has not been tested under representative conditions.

Capacity: can the responsible teams deliver the next commitment? Establish whether the people needed for decisions, testing and adoption are available. A plan that depends on specialists already committed elsewhere needs an explicit priority decision.

These dimensions belong in one discussion because a change in one can alter the others. Extending parallel operation affects cost. Removing scope can protect a date while reducing the expected benefit. Adding capacity may shorten a delay, provided capacity is the actual constraint.

Corrective action starts with the cause

Suppose adoption is below expectation. More training is one possible response. It would have little effect if employees are avoiding the process because it cannot handle their exceptions.

I would first establish where the work breaks down, which teams are affected and who has authority to resolve it. Leadership then needs feasible options with their consequences: correct the workflow, change the operating responsibility, reduce the rollout scope or accept a longer transition.

The recommendation should make the trade-off explicit. Protecting a launch date may mean postponing functionality. Protecting continuity may justify a temporary additional cost. Continuing unchanged also carries consequences, including prolonged duplicate work.

An executive review should make those choices visible early enough for someone to act.

Every review needs a decision that can be checked

For a material issue, I would want the review to end with a recorded decision, an accountable owner, a deadline and the evidence expected at the next review. Where authority sits across several functions, the decision route needs to be explicit.

“Business and IT to resolve” leaves too much open. Someone must be accountable for securing the decision, with named contributors responsible for their part.

The next review should examine whether the agreed action changed the position. If the same issue returns with the same explanation, leadership needs to revisit the intervention, the authority behind it or the feasibility of the commitment.

Fund the next constraint

When delivery is progressing and the benefit remains credible, continue with clear conditions. When an operating constraint is preventing the benefit, direct the next intervention towards that constraint. When the expected return no longer justifies the remaining cost and risk, reconsider the scope or the investment.

In the workflow example, the next priority might be resolving exception ownership and retiring duplicate approvals. Another feature release could consume budget while leaving both problems in place.

Before approving the next phase, I would ask for one clear statement: what business improvement will this commitment unlock, who owns it, and when will we have evidence?