What Capability Looks Like When It Has Actually Been Built

The question that tends not to get asked honestly at the end of a major development programme is whether the people who went through it can now do something they could not do before - not within the structured environment of the programme itself, but on an ordinary working day six months later when the support has ended and the problem is real.

Most organisations do not ask this question, partly because the answer is harder to measure than programme completion and partly because, if answered honestly, it often reveals that people know considerably more than they did but are not yet reliably doing more than they did. Knowledge and capability are not the same thing, and the distance between them is where most development investment quietly disappears.

Knowledge is what people can recall and articulate: the governance framework, the model for handling difficult conversations, the approach to building psychological safety discussed in the workshop. Capability is what people actually do under pressure when no one is directing them. The difficult conversation that gets had because the person leading it has developed through having real ones, not constructed ones. The decision made at the right level because the person responsible has built judgement through practice, not through instruction. The team that names its own dysfunction rather than waiting for an external presence to create permission for the conversation.

The NHS Hospital 2.0 programme makes this distinction both urgent and specific. Delivering 46 hospitals over two decades requires the NHS to be a capable and intelligent client not only for the first programme in the sequence but across the full 20-year horizon, in conditions where the delivery environment will change, key individuals will move on, and the pressures on the system will shift in ways nobody can fully anticipate now. Knowledge from early programmes, however well captured in lessons-learned documents and guidance frameworks, will not by itself transfer the capability to make good decisions under pressure in the programmes that follow. Whether it does depends on how that knowledge was developed, and whether the people carrying it had the opportunity to build genuine capability rather than receive instruction.

Developing capability rather than delivering knowledge requires a different design for how people learn through a programme. It means working through real challenges rather than constructed ones, because capability develops in the doing of actual work rather than in the rehearsal of scenarios designed to simulate it. It means the support available during those real challenges is present when the difficulty is happening, not in the preparation beforehand. And it means the challenge within that support is genuine: people develop through being held to honest account for how they are performing rather than being managed through discomfort without having to face it squarely.

This is what challenge, support, evolve means in practice, and it is worth being precise about what that means, because the structure matters. It is not a linear progression where challenge happens first, support follows, and evolution arrives at the end. It is a simultaneous approach to every interaction and every development moment throughout the programme. The challenge is what makes the learning real rather than comfortable. The support is what makes it possible to engage with honestly rather than avoid. The evolution is what the person and the organisation carry forward when the programme ends, because the capability was developed through their own experience under real conditions rather than received as content to be absorbed.

For Hospital 2.0, and for any organisation investing in sustained development across complex and extended programmes, the test of whether development worked is not visible in the end-of-programme evaluation. It is visible in what happens on an ordinary morning six months later, when a project leader faces a genuine commercial disagreement between partners, a relationship under pressure, and a delivery timeline at risk, and has to decide whether she has the capability to work through it independently or the habit of looking for someone to tell her what to do.

One of those is the end state of training. The other is the end state of development.

What would that morning look like in your organisation, and which answer would you want to be confident about?

References

NHS England (2025) New Hospital Programme / Hospital 2.0.
Major Projects Association (2025) Mobilisation Perspectives Report, February 2025. Resource available to MPA members only
UCL Bartlett School of Sustainable Construction, Addyman (2023) Exploring the Role of a Programme Delivery Partner.