From programme to product: Rethinking internal enablement in government

For public sector organisations, starting a transformation is usually a success. Unfortunately, the struggle often comes soon after, with sustaining these changes and achieving lasting outcomes. 

The transformation journey typically starts with building products or services, usually with external consultancies, and training Civil Servants. But eventually, the external consultancy leaves, and teams revert to familiar ways of working faster than anyone expects. Despite everyone’s best efforts, impact fizzles out. 

Consultancies often promise to build internal capability as part of a programme, but it rarely results in lasting confidence once the work is complete. The reason is simple: enablement is treated as a tick-box exercise, rather than as a blueprint for leaving behind genuinely capable people who can continue to build, improve and sustain services over the long term.

If capability is going to last, enablement needs to be treated as a product. This means programmes designed to reach completion, and products designed to evolve. That emphasis is a key distinction.

Programme thinking vs product thinking

When enablement is shaped by programme thinking, the focus is on completing a set of activities. Once the consultancy has run training, introduced tools, and handed over ownership, the work is considered done. In reality, the boxes may have been ticked, but capability is still forming.

A product mindset changes how we define a successful transformation. We look further than whether enablement has been delivered, and instead assess whether it is working and improving over time.

There is, however, a fundamental issue that often gets missed. Capability is not proven through training or awareness. It is proven through delivery.

Capability through delivery 

If teams are not given the space and responsibility to deliver meaningful work themselves, enablement remains theoretical. People may understand new approaches, but without applying them in practice, they won’t form the necessary confidence and capability.
Real enablement happens when teams use their skills in work that matters. This means work with outcomes, accountability and consequence. Work that stretches their judgement and builds trust in their ability.

Product enablement in practice

At Counter, we have seen this play out in practice through our work with HMRC. Facing a need to reduce long-term reliance on external suppliers while still delivering at pace, HMRC took a deliberate step away from traditional consultancy models. Instead of bringing in external teams to deliver work on their behalf, they created blended teams where internal staff and experienced practitioners worked together on live services.

This went further than shadowing or observation. Internal teams were directly involved in shaping solutions, making decisions, and owning outcomes. They worked on real delivery challenges, from improving existing services to tackling more complex transformation activity.

That distinction was critical. The work was real, so capability was developed in context. Teams didn’t just see new ways of working; they applied them, adapted them, and took accountability for the results.

Over time, this changed how capability showed up across the organisation. Confidence increased because teams had delivered successfully themselves. Decision-making became stronger because people understood not just what to do, but why. External support shifted from leading delivery to reinforcing and extending internal capability.

It also changed the economics of delivery. As internal capability strengthened, HMRC reduced its reliance on traditional sourcing models, giving it greater control over how services were developed and improved.

Most importantly, the capability that emerged was grounded and resilient. It had been tested through real delivery, aligned to real priorities, and embedded in the teams responsible for continuing the work.

Shifting from programme to product

Treating enablement as a product creates the conditions for successes like HMRC’s to happen more consistently.

It encourages continuous improvement, where capability is strengthened based on how teams are actually performing. It places ownership closer to delivery, where capability is shaped day to day. And it creates ongoing feedback loops so that support, tools and ways of working evolve alongside organisational needs.

At its core, this is a shift in thinking from simply finishing internal enablement, to actually owning it. And when enablement is treated as a product, shaped through real delivery and continuous use, it becomes the foundation for capability that lasts.