When does a programme become business as usual?

A surprising amount of value is lost in the quiet moment when a programme is supposed to become business as usual. The build succeeds, go-live happens, the programme celebrates and disbands, and a few months later the thing it delivered is underused, poorly run, or quietly degrading, because the transition into operations was treated as an afterthought rather than a decision.

The first problem is that go-live is mistaken for the finish line. For a programme, go-live can feel like the end. For the organisation, it is the beginning of the period where the benefits are actually meant to be realised. Treating the launch as the win is how programmes hit their dates and still fail to deliver value, because the value was always going to come from operation and adoption, not from the deployment itself.

The second problem is that the handover often has no owner on the receiving side. A programme is, by design, temporary, and it is motivated to declare done and move on. Operations is permanent, and frequently inherits something it had little hand in shaping, with no warning and no capacity. When no one owns the catch, the thing gets dropped, and it is dropped slowly enough that no single moment looks like the failure.

The transition has to be planned as deliberately as the build. Who runs this once the programme is gone, do they have the capacity and capability to do it, when does accountability formally move, and what does the programme owe the operational team before it is allowed to stand down. These are questions to answer early, not in the final fortnight when the team is already half gone and the budget is spent.

There is also an honesty point about when to declare BAU. A programme under pressure has every incentive to call something operational before it really is, because that lets the programme close on time. Declaring BAU is not an administrative step. It is a statement that the thing genuinely runs without programme support, and it should be earned, not asserted to hit a date.

For an executive, the question worth asking well before go-live is simple. Who owns this the day after the programme ends, and are they ready. If that has no clear answer, the programme is heading for a clean launch and a messy aftermath, and the aftermath is where the value lives.