Who owns a capability after the project team leaves?

A capability does not look after itself. Once the project team that built it has moved on, someone has to run it, fund it, improve it and answer for it. Surprisingly often, no one clearly does. The capability keeps working for a while on the momentum of its launch, and then begins a slow decline that is nobody's specific job to notice until it has become a problem.

The root of this is that building and owning are different responsibilities, and organisations are much better at resourcing the first. A programme is set up, funded and staffed to deliver. Ownership of the result afterwards is often assumed rather than assigned, left to fall on whichever operational team is nearest, frequently without the budget or the mandate to actually take it on.

The clearest symptom is the capability that slowly decays. The integrations that no one maintains until they break. The process that quietly reverts to the old way because no one owned embedding the new one. The tool that everyone was trained on and few still use, because adoption was someone's job during the project and no one's job after it. None of these is a dramatic failure. Each is the predictable result of a capability with no owner.

Real ownership, here as everywhere, means more than a name on a chart. It means someone with the budget to keep the thing healthy, the authority to make decisions about its future, and the accountability when it fails. If the named owner has the title but not the budget, they will watch it degrade and be unable to stop it, which is worse than having no owner at all, because it looks covered when it is not.

The time to settle this is before the programme ends, not after the first thing breaks. Part of what a programme owes the organisation is a clear, accepted answer to who owns what it built, confirmed by someone who has actually agreed to take it, with the means to do so. A handover accepted by a team that has no capacity to honour it is not a handover. It is a deferral.

For a leader, the test is to take any capability delivered in the last two years and ask who owns it now, and whether they have what they need to keep it alive. The answers tend to reveal where the next avoidable problem is already forming.