PCPM All articles
Benefits Realisation

Twelve Months After Go-Live: Keeping an Honest Account of Operational Change

PCPM
Twelve Months After Go-Live: Keeping an Honest Account of Operational Change

Photo: UK operations manager reviewing performance metrics twelve months after system launch, via as2.ftcdn.net

A project can be delivered to time, cost and scope and still leave the day job essentially unchanged. The new system is live, the training has been delivered and the closure report has been signed. Six months later, staff are still maintaining the old spreadsheet, the expected efficiency saving has not appeared in any budget and a new manual workaround has quietly become part of the process.

Go-live is a delivery milestone. It is not proof of operational change. For UK organisations seeking clearer delivery, the missing control is often a longer-term account of what actually happened after implementation. A twelve-month benefits ledger provides that account.

Why twelve months

Some benefits appear quickly. A licence cost may fall as soon as a legacy system is switched off. Other benefits take longer. New ways of working need to be adopted, old processes need to be retired, and managers need to trust the new information enough to stop duplicating it. Twelve months is not a arbitrary period, but it is long enough to see whether adoption has stuck and short enough to retain organisational memory.

A twelve-month ledger also creates a useful discipline at the point of approval. If the business case promises operational benefits, the delivery team should know from the outset how those benefits will be evidenced a year after go-live. That changes the conversation from proving success at closure to learning whether the operation actually changed.

The ledger is not a scorecard

The purpose of the ledger is not to grade the project team. It is to record what happened in the operation, including the parts that were not planned. A ledger that only records realised savings will miss the unintended operational costs that often determine whether a change is genuinely worthwhile.

The ledger should therefore have four columns, each with an owner and an evidence source.

The first is adopted ways of working. This records which new processes are actually being used, by whom and how consistently. Evidence might include system logs, audit samples, process observations or manager confirmation. The key question is not whether training was completed, but whether the old method has stopped.

The second is realised savings. This should distinguish cash-releasing savings from notional savings. A reduced headcount or a cancelled contract releases cash. A time saving that has not been converted into capacity or reduced expenditure is a productivity gain, not a budget saving. Both can be valuable, but they should not be conflated.

The third is unintended operational costs. These include additional support calls, manual reconciliation, shadow systems, extra training, temporary staff and management overhead. They are easy to overlook because they often sit outside the project budget. They are essential to an honest verdict.

The fourth is evidence and ownership. Each line should have a named owner and a source that can be checked. Without that, the ledger becomes a collection of impressions.

Set the opening balance at go-live

The ledger needs a baseline. At or shortly before go-live, the organisation should record the current operational position for each benefit line. That might include processing times, error rates, staff hours, supplier costs, customer contact volumes and the prevalence of workarounds. The baseline does not need to be perfect. It needs to be explicit enough that later claims can be tested.

The opening balance should also record the assumptions behind the expected benefit. If the business case assumed that 80 per cent of transactions would be handled through the new channel within six months, that assumption should be visible. If it assumed that two legacy roles would be removed after three months, that should be visible too. The ledger can then show whether the assumption held.

Quarterly checkpoints

A twelve-month ledger does not need monthly reporting. Quarterly checkpoints are usually sufficient, with a final review at month twelve. Each checkpoint should ask four questions.

Are the new ways of working actually in use? This is an adoption question, not a satisfaction question. It should be answered with evidence, not anecdote.

Have the expected savings been realised, and in what form? The answer should distinguish cash, capacity and avoided cost.

What new operational costs have appeared? These should be recorded even if they are small, because they often accumulate.

What decisions are needed? If adoption is lagging, the ledger should prompt a decision about training, process change, management attention or, in some cases, stopping the benefit claim.

The quarterly review should be owned by the operational leader who now runs the process, not by the project manager who delivered it. The project manager may attend, but accountability for the day job sits with the operation.

The month-twelve verdict

At month twelve, the organisation should be able to place each benefit line into one of five categories: realised, partially realised, displaced, not realised or unintended cost. Displaced is a useful category for benefits that have moved elsewhere in the organisation rather than disappeared. Not realised is not a failure of the ledger. It is the information the ledger exists to produce.

The verdict should lead to a decision. Benefits that are realised may justify further investment or a change to the target operating model. Benefits that are partially realised may need a corrective plan. Benefits that have not been realised may need to be written back in the business case, with a clear explanation. Unintended costs should be added to the operational budget and, where possible, designed out.

Independence and evidence

A benefits ledger is more credible when it is not self-assessed by the delivery team alone. Finance should validate cash claims. Operations should validate adoption. The programme management office can maintain the ledger and test the evidence, but it should not be the only source of assurance.

Sampling is usually enough. A small number of observed processes, system reports and manager interviews will reveal more than a comprehensive spreadsheet completed in isolation. The aim is a reasonable account, not a forensic audit.

Closing the account

The twelve-month ledger is not an exercise in blame. It is a way of closing the loop between delivery and operations. Projects are approved on a promise of change. The ledger tests whether that change arrived, what it cost and what the organisation learned.

For UK organisations facing constrained budgets and competing priorities, that test matters. Clearer delivery does not end at go-live. It ends when the operation can show, with evidence, that the day job has genuinely moved.

All Articles

Related Articles

The Unofficial Timetable: Reconciling the Plan Teams Actually Work To

The Unofficial Timetable: Reconciling the Plan Teams Actually Work To

Passing the Baton Without Dropping the Promises: A Post-Award Week One Protocol

Passing the Baton Without Dropping the Promises: A Post-Award Week One Protocol

Assurance at One Remove: Seeing the Subcontractor Layer Without Owning It

Assurance at One Remove: Seeing the Subcontractor Layer Without Owning It