Building digital capability in the Public Sector: Growing skills through delivery

Digital transformation in the public sector is often framed around technology. New platforms, modern architecture, automation, AI, and service redesign usually dominate the conversation. But in practice, successful delivery rarely comes down to technology alone. More often, it comes down to people — the capability within teams to design, deliver, improve, and sustain digital services over time.

Over the last few years, I have worked alongside public sector teams delivering large-scale digital change across complex environments. One thing has become consistently clear: the narrative that government lacks digital capability is both inaccurate and unhelpful. Some of the strongest delivery practitioners I have worked with have been within the public sector itself. The depth of operational knowledge, policy understanding, service awareness, and commitment to users is often exceptional.

The real challenge is not an absence of digital skills. It is how organisations scale capability, retain knowledge, create space for learning, and sustain delivery under constant pressure. Digital teams are often expected to modernise services while simultaneously managing legacy systems, policy change, operational demand, procurement constraints, and recruitment challenges. That creates pressure not because teams are incapable, but because expectations continue to grow faster than organisational capacity.

For leaders responsible for digital delivery, this creates an important shift in thinking. The focus should not be on “fixing” capability gaps through short-term recruitment alone. Instead, it should be on building environments where capability can grow sustainably through delivery itself.

The challenge is often capacity, not capability

One of the most common misconceptions I encounter is the assumption that delivery problems stem from a lack of skilled people. In reality, many public sector teams already contain highly experienced business analysts, service designers, delivery managers, developers, architects, and operational specialists. The issue is often that those individuals are stretched across too many priorities at once.

I have seen teams managing several major programmes simultaneously while also supporting live services, responding to ministerial priorities, and dealing with evolving operational pressures. Under those conditions, even strong teams can struggle to create the space needed for capability development, mentoring, experimentation, or reflective improvement.

This is particularly visible during periods of rapid transformation. Organisations understandably focus on delivery pace and outcomes, but capability growth can become secondary. Training budgets are reduced, discovery activities are shortened, and teams become increasingly reactive. Over time, this creates dependency on a small number of experienced individuals who carry significant delivery knowledge.

From a business analysis and service design perspective, this is where practitioners can play an important enabling role. Good analysts and designers do more than produce artefacts or facilitate workshops. They help create shared understanding across teams. They surface operational knowledge, clarify decision-making, and reduce reliance on tribal knowledge that sits with individuals.

I have worked on programmes where relatively small improvements in collaboration and documentation significantly reduced delivery friction. Mapping service journeys properly, aligning stakeholders around processes, and making operational knowledge visible often created more value than introducing entirely new tooling. In many cases, capability already existed within teams — it simply needed the right conditions to become scalable and sustainable.

“From the outset, what stood out was the way the consultancy integrated with our existing teams rather than operating separately from them. There was a genuine focus on building capability within the programme while still maintaining delivery momentum. Their analysts and service specialists helped create structure around complex delivery challenges, but they also brought people with them throughout the process. By the end of the engagement, we had not only progressed the service significantly, but our internal teams were more confident, more aligned, and better equipped to continue the work themselves.”

Head of Digital Delivery

Building capability through delivery, not around it

One of the biggest mistakes organisations can make is treating capability development as something separate from delivery. In pressured environments, standalone training programmes often struggle to gain traction because teams simply do not have the time to step away from live work for extended periods.

The most effective public sector teams I have worked with tend to build capability directly into delivery activity itself.

This can happen in relatively simple ways. Pairing less experienced analysts with senior practitioners during discovery work. Running collaborative mapping sessions instead of isolated requirements gathering. Involving operational teams in service design conversations earlier. Encouraging shadowing during stakeholder engagement or research playback sessions.

These approaches are not always formally labelled as “up-skilling”, but that is effectively what they achieve. They allow capability to grow in context, grounded in real services and real delivery pressures.

I have seen this work particularly well when consultancies or contingent specialists position themselves as embedded partners to delivery teams rather than external experts arriving with predefined answers. The best outcomes usually happen when external support actively transfers knowledge into permanent teams instead of creating long-term dependency.

That means being transparent in how decisions are made. Explaining approaches rather than simply delivering outputs. Creating reusable artefacts. Bringing internal teams into facilitation and decision-making rather than shielding them from complexity.

In my experience, public sector teams respond particularly well to collaborative delivery models because they already possess deep contextual understanding of their services and users. External specialists can help accelerate delivery or introduce additional methods, but sustainable transformation only happens when capability becomes embedded internally.

Recruitment alone will not solve the problem

Recruitment remains an important part of digital workforce planning, but it is rarely sufficient on its own.

Public sector organisations continue to face strong competition for experienced digital professionals, particularly in specialist areas such as architecture, cyber security, product management, and service design. Salary constraints and procurement cycles can make rapid scaling difficult, especially when compared to parts of the private sector.

However, focusing exclusively on recruitment risks overlooking the capability that already exists within organisations.

Some of the strongest digital practitioners develop internally through exposure to delivery environments over time. Operational staff often possess deep service knowledge that can become incredibly valuable when combined with digital skills and delivery experience. I have seen excellent analysts emerge from operational backgrounds because they understood both user needs and organisational realities in a way that purely technical specialists sometimes did not.

This is why workforce development should not be viewed purely through the lens of hiring externally. It should also involve creating clearer pathways for internal growth.

That may mean supporting operational staff into digital roles. Giving junior practitioners opportunities to lead smaller workstreams. Creating multidisciplinary teams where learning happens naturally through collaboration. Or simply ensuring experienced practitioners have enough time to mentor others properly.

There is also an important cultural element here. Organisations that openly value learning tend to retain capability more effectively. Teams are far more likely to stay engaged when they feel they are growing professionally rather than simply managing delivery pressure indefinitely.

“One of the biggest benefits of the engagement was the collaborative approach taken with operational and policy colleagues. There was never an assumption that external specialists had all the answers. Instead, the consultancy worked closely with our teams to surface knowledge that already existed within the organisation and translate that into practical delivery improvements. That created a much stronger sense of ownership across the programme and helped us build capability in a sustainable way rather than relying on long-term external dependency.”

Senior Programme Lead

The role of leadership in creating sustainable teams

Digital capability is heavily shaped by leadership behaviours, even when leaders are not directly involved in delivery activity itself.

Where I have seen transformation programmes succeed long term, leaders usually create conditions that allow teams to work sustainably. They protect discovery time. They encourage multidisciplinary collaboration. They support iterative delivery rather than demanding certainty too early. And importantly, they recognise that capability growth requires patience.

One of the risks in large-scale transformation is the pressure to demonstrate rapid progress through visible outputs alone. Under that pressure, organisations can unintentionally create environments where delivery becomes transactional. Teams move from deadline to deadline without time to reflect, improve processes, or invest in knowledge sharing.

The consequence is often hidden capability debt. Services may continue to move forward, but resilience within teams gradually weakens. Knowledge becomes fragmented, onboarding slows down, and dependence on key individuals increases.

Strong leadership helps counter this by viewing capability as part of delivery itself rather than an optional extra.

I have worked with senior leaders who deliberately structured programmes to encourage cross-functional learning. In some cases, that meant rotating responsibilities across teams. In others, it meant ensuring suppliers worked closely alongside permanent staff rather than independently. Sometimes it was as simple as creating regular opportunities for teams to reflect openly on delivery challenges and lessons learned.

Those environments tended to produce stronger outcomes not only because delivery improved, but because organisational confidence improved alongside it.

Digital transformation is ultimately about confidence

When people talk about digital capability, discussions often focus on frameworks, skills matrices, or workforce strategies. Those things matter, but capability is also deeply connected to confidence.

Teams that feel trusted, supported, and involved in decision-making are usually far more willing to experiment, collaborate, and improve services iteratively. Teams operating under constant pressure and scrutiny often become understandably risk-averse.

This is particularly important within government environments where accountability is high and services directly affect people’s lives. Public sector teams carry significant responsibility, and that can sometimes create caution around change. But I have consistently found that when practitioners are given the space to engage meaningfully with users, test ideas, and collaborate openly, innovation follows naturally.

Business analysts and service designers can play an important role in creating that confidence. Not by positioning themselves as owners of transformation, but by helping teams navigate complexity together. Good facilitation, clear communication, and structured collaboration often create the conditions where confidence begins to grow across a programme.

In many ways, sustainable digital transformation is less about introducing entirely new capability and more about unlocking, connecting, and strengthening the capability that already exists.

“We were operating in a high-pressure environment with multiple delivery priorities competing for attention. What the consultancy brought was not just additional capacity, but clarity and confidence. Their approach to business analysis and service design helped connect technical teams, operational staff, and senior stakeholders in a way that improved decision-making across the programme. Importantly, they invested time in mentoring and supporting our permanent teams throughout delivery, which meant the organisation retained valuable knowledge and capability long after the project phase had ended.”

Director of Transformation

Final thoughts

The public sector already contains significant digital expertise, delivery experience, and operational understanding. The challenge facing many organisations is not whether capability exists, but how to sustain and scale it in increasingly demanding delivery environments.

That requires moving beyond the idea that transformation can be solved purely through recruitment or technology investment. Sustainable progress comes from creating delivery cultures where learning, collaboration, and capability development happen continuously alongside delivery itself.

For me, some of the most successful programmes have been the ones where knowledge was openly shared, multidisciplinary teams worked closely together, and external support focused on strengthening internal capability rather than replacing it.

Digital transformation is ultimately a long-term organisational effort, not a short-term delivery exercise. The organisations that succeed will likely be the ones that invest not only in technology and services, but in the confidence, growth, and resilience of the people delivering them.

As public sector delivery continues to evolve, perhaps the more useful question is not whether government has the digital skills it needs today — but whether we are creating the conditions for those skills to grow sustainably tomorrow.