The Second Shift After Go-Live: Making Absorbed Effort Visible

Go-live is often presented as the moment a change programme hands over. In practice, it is closer to a change of shift. The project team steps back, and business-as-usual colleagues step forward—often into duties that were never fully priced, scheduled or agreed. The difficulty is not that BAU teams are unwilling. It is that the additional work is frequently absorbed rather than acknowledged, and absorbed effort is easy to overlook until capacity gives way.

Where the work actually lands

Post-go-live effort rarely arrives as a single, visible transfer. It tends to appear as a series of small adjustments: resolving data exceptions, answering queries about new screens, maintaining workarounds while defects are fixed, producing reports that used to be generated by the project, attending additional governance meetings, and explaining the new process to customers or suppliers. In UK organisations, these tasks often fall to team leaders and experienced practitioners who are already carrying day-to-day operational demands.

The pattern is familiar across local authorities, financial services, retail operations and professional services. A new system may replace an old one, but the surrounding ecosystem—spreadsheets, checklists, informal knowledge and escalation routes—does not disappear on command. Someone must keep it running while the formal solution matures. That someone is usually in BAU, and their contribution is rarely recorded as programme cost.

The hidden cost of absorption

When effort is absorbed, it does not vanish. It is paid for through overtime, deferred improvement work, slower customer response, reduced attention to compliance checks, or the quiet erosion of morale. The organisation may report a successful go-live while operational teams are still carrying the change in the background. This is not a failure of commitment; it is a failure of visibility. If the delivery team cannot see the work, it cannot support it, sequence it, or decide whether to stop doing something else.

The commercial dimension matters too. Suppliers may declare completion against contractual criteria while BAU colleagues continue to provide unofficial support. Without a record of that effort, there is little evidence for conversations about warranty periods, service credits, transition support or future funding. The result is a gap between what the contract says and what the operation actually requires.

A simple absorption register

An absorption register need not be elaborate. Its purpose is to make invisible work visible without creating another bureaucratic ritual. A spreadsheet or a short section in the programme's benefits tracker is usually sufficient. For each entry, record the date, the source of the activity, a brief description, the team and named owner, an estimate of time or frequency, the operational impact, and the decision or action required.

Key fields might include:

• Activity or issue: what is being absorbed.
• Origin: project defect, process gap, reporting request, supplier query or training need.
• Frequency: one-off, daily, weekly or unknown.
• Estimated effort: hours per week or per month, with a confidence note.
• Impact: displaced work, overtime, risk or customer effect.
• Owner: the BAU lead accountable for the activity.
• Decision: accept, automate, eliminate, fund or escalate.

The register should be reviewed weekly during the first 90 days after go-live, then monthly until the activity is either closed or formally transferred. It is not a blame log. It is a capacity and accountability tool. Its value lies in turning anecdote into evidence that delivery leaders can act on.

Questions before signing off completion

Before a change is declared complete, delivery leaders should ask a set of practical questions. Who in BAU has accepted each new duty, and has that acceptance been matched with capacity? Which tasks will stop when the project ends, and who has confirmed that they are genuinely stopping? What evidence exists that data quality, reporting definitions and support routes are stable enough for BAU to own? Have training and documentation been tested against real operational scenarios, not just attendance records? What is the escalation route for defects and queries after the project team disbands? Which decisions remain with the supplier, and which sit with the business? What will be reviewed at 30, 60 and 90 days, and who owns that review? If additional effort is required, will it be funded, automated or explicitly accepted as a trade-off?

These questions are not designed to delay closure. They are designed to make closure honest. A programme that ends with an unrecorded operational subsidy is not fully complete; it has simply moved its costs to a less visible ledger.

Clearer delivery after the ribbon

The test of a change is not whether the project team can leave the building. It is whether the operation can carry the change without hidden strain. Making absorbed effort visible gives BAU teams a fair hearing, gives delivery leaders better evidence, and gives the organisation a more accurate account of what the change actually costs. Go-live may mark the end of the project, but it starts a second shift in the business. That shift deserves a plan, an owner and a proper record.