Ask a transformation programme who operates the thing it's building, twelve months after launch, and you will usually get one of three answers. Business as usual. The existing team. Or a pause.
None of those is a plan. The first two are ways of saying not us, and the pause is the honest one.
"Go-live is the moment a programme stops and an operation starts. Most organisations fund only the first half of that sentence."
— Paul Balaam, Rewired+PartnersThe structural gap
Business cases are written to get funding approved, and funding approval is about building things. So the case covers discovery, design, build, integration, migration, testing and launch — and stops.
The operating cost that follows is either a line item nobody scrutinised or a sentence saying the platform will be absorbed into existing teams. Which is fine if those teams have the capacity, the skills and the mandate. They usually have none of the three, because they were fully occupied running the thing this replaces.
What follows is predictable. The new platform gets maintained rather than developed. The data it produces goes unexamined because analysing it isn't anyone's job. Within eighteen months the organisation has a modern system operated exactly like the legacy one — which is to say, kept alive.
Design the operators alongside the platform
The programmes that hold their gains build the operating team as a deliverable, not as a consequence.
On the union programme, it was clear early that the technology launch had to coincide with a redesign of how the organisation actually worked. Two operating models were built alongside the platforms. A communications model that returned national messaging to the national team so regions could concentrate on their members' most pressing issues. And a product operations function — a new team, created to run the new platforms and use live data to keep improving them.
For the professional body we worked with, the lasting outcome of a £5M+ transformation wasn't the platform either. It was two new internal operating teams — content operations and product operations — who run the roadmap today.
In both cases the teams existed before go-live. That timing is the whole point: a team stood up afterwards inherits decisions it had no part in and a backlog it didn't write.
The questions that expose it
- Whose job changes? If nobody's does, nothing has transformed — you've bought software.
- Who looks at the data on a Tuesday? Real-time insight is worthless without someone whose role is to act on it.
- Who decides what gets improved next? If the answer is a steering group that disbands at closure, there is no answer.
- What is the operating cost in year three? If the business case doesn't say, it hasn't been thought about.
- Where do these people come from? New roles, redeployment or backfill — all fine. Silence is not.
It's cheaper than it sounds
The objection is always cost, and it's the wrong way round.
A product operations function is small — a handful of people. Set against a multi-million-pound programme, it's a rounding error. Set against the cost of that programme delivering a fraction of its benefits because nobody was resourced to realise them, it's the cheapest line in the case.
Benefits don't arrive at go-live. They accumulate afterwards, through the people paying attention. Fund the operators, or accept that the business case was a work of fiction from the moment it was signed.
