Strengthening digital capability in Government: People, Skills and Culture

Digital transformation starts with people

Government organisations have invested heavily in digital transformation. New platforms have been introduced, legacy services are being modernised and teams are adopting agile and user-centred approaches. Yet one of the most persistent challenges I see is not technology. It is capability.

A government organisation can have a modern technology platform and still struggle to deliver a good service. It can have an agile delivery framework and still make decisions slowly. It can recruit experienced digital specialists and still fail to build the capability needed to sustain change.

The reason is simple. Digital transformation changes how people work.

It changes how teams understand problems, make decisions, engage with users, work with technology and measure success. It also changes the skills people need. A programme that introduces a new digital service may require business analysts to understand service ecosystems, policy teams to work more closely with delivery teams, senior leaders to make decisions using evidence and operational staff to work confidently with new technology.

I have seen this repeatedly across government projects. The technical solution is often only one part of the challenge. The harder question is whether the organisation is ready to use, maintain and improve that solution once it is delivered.

This is why digital capability needs to be treated as part of transformation itself, rather than as a separate training activity.

Training is necessary, but it is not enough. Government needs people with the right skills, opportunities to apply those skills and a culture that allows them to work effectively.

Capability is more than sending people on courses

When organisations identify a capability gap, the instinct is often to look for training.

Someone needs to understand agile, so they attend an agile course. A team needs to improve its understanding of user research, so a workshop is arranged. A new technology is introduced, so staff receive technical training.

These interventions can be useful, but they rarely solve the underlying problem on their own.

Capability is demonstrated through behaviour and outcomes, not attendance.

A person can complete a service design course without becoming a better service designer. A team can learn the principles of agile without changing how it makes decisions. An organisation can publish guidance on user-centred design without giving delivery teams the time, access or authority to understand users properly.

I therefore think about capability development in three connected layers.

The first is knowledge: understanding the methods, tools and principles required for a role.

The second is practical ability: being able to apply that knowledge to a real problem, with all the constraints and uncertainty that government delivery brings.

The third is organisational environment: whether the surrounding culture, leadership and governance allow people to use those skills effectively.

All three matter.

Consider a business analyst working on the replacement of a legacy government system. They may have strong analytical skills and understand modern requirements practices. But if the programme expects a complete set of requirements before users can be involved, or if senior stakeholders make decisions without evidence, their ability to apply those skills will be limited.

The capability problem is not necessarily the individual.

It is the system around them.

This distinction matters because otherwise organisations can spend significant amounts of money developing people while leaving the conditions that prevent them from succeeding unchanged.

“The value of the engagement went well beyond the immediate project deliverables. The team brought a level of challenge and structure that helped us understand not only what we needed to change, but why. They worked alongside our people rather than simply delivering something and moving on, and that made a real difference. Our teams became more confident in using user-centred and agile approaches, and we were left with stronger internal capability that we could continue to build on after the engagement ended.”

Head of Digital Delivery, Central Government Department

Develop capability through real delivery

The most effective development I have experienced has usually happened alongside delivery rather than away from it.

Government projects provide an unusually rich environment for learning. Teams are working with real users, real policy constraints, real operational processes and real technical limitations. These are much better learning environments than abstract exercises.

A junior business analyst, for example, can learn far more by being supported through a real discovery than by simply reading about discovery. They can learn how to frame a problem, how to challenge assumptions, how to structure stakeholder conversations and how to turn research into useful evidence.

The same applies to service design.

Mapping a real service exposes complexity that a training exercise often cannot. A service designer has to work out where ownership sits, understand dependencies between teams, identify gaps in the user journey and make sense of systems that may have evolved over many years.

This is where experienced practitioners have an important role.

Capability building does not always require a formal training programme. Pairing, coaching, communities of practice, structured peer review and working alongside experienced specialists can transfer knowledge continuously.

I have found this particularly valuable when introducing new ways of working. Rather than simply telling a team how to create a service map, for example, I would rather work through the mapping with them and explain the decisions being made. The team then develops both the artefact and the judgement required to create the next one independently.

This also creates a more sustainable model.

The objective should not be to make an organisation permanently dependent on external specialists. External expertise can be extremely valuable, particularly when a capability needs to be established quickly or when specialist experience is unavailable internally. But the strongest engagements leave knowledge behind.

A good consultant should make the organisation stronger, not simply complete the work on its behalf.

“One of the biggest challenges we face in government is making sure that the knowledge and capability developed through a transformation programme stays within the organisation. This engagement was particularly valuable because the consultancy did not operate as an external team working separately from ours. They actively involved our people, explained the thinking behind the approach and helped practitioners develop their own skills through the work. That has given us a much stronger foundation for delivering future change and, importantly, greater confidence in our own teams.”

Programme Director, Government Transformation Programme

Build digital capability across disciplines

Digital delivery is often described in terms of specialist roles: business analysts, service designers, user researchers, developers, delivery managers, architects and content designers.

Those specialisms remain important. However, some of the most valuable capability is increasingly shared across disciplines.

A policy professional does not need to become a service designer. But they should understand why user research matters and how evidence can influence policy decisions.

A senior leader does not need to become an agile practitioner. But they should understand why delivery teams need clear outcomes, empowered decision-making and space to learn.

An operational manager does not need to become a technical architect. But they should understand how technology decisions can affect the service they operate and the experience of the people who use it.

This is particularly important in government because digital services rarely belong to one team.

A user journey may cross policy, operations, technology, communications and multiple organisations. Improving one part of the service without understanding the wider system can simply move the problem somewhere else.

Business analysts and service designers can play an important role in connecting these perspectives.

The BA can help translate between policy intent, business needs, user needs and technical delivery. The service designer can help teams understand the wider service and the relationships between people, processes, technology and organisations.

Neither role should operate as a documentation function at the edge of delivery.

They should help create shared understanding.

That shared understanding is itself a form of organisational capability. When teams develop a common language for describing problems, outcomes, users, services and dependencies, they become better equipped to make decisions without relying on a small number of individuals to hold all the knowledge.

Culture determines whether skills become capability

Even highly skilled people can struggle in an organisation that does not support effective digital delivery.

This is often the least visible part of capability building because culture is harder to measure than training completion.

A team may have the skills to work iteratively, but if governance expects certainty at the beginning of a project, iteration becomes difficult.

A team may know how to conduct meaningful user research, but if access to users is repeatedly delayed, that capability cannot influence decisions.

A delivery team may understand how to prioritise work around outcomes, but if senior stakeholders continue to measure progress through the volume of features delivered, behaviour will eventually follow the measurement system.

Culture is shaped by what an organisation rewards, tolerates and measures.

This means leaders have a significant role in digital capability. They do not need to become experts in every digital discipline, but they need to create the conditions in which those disciplines can operate effectively.

That includes giving teams appropriate autonomy, creating space for learning, encouraging evidence-based decisions and treating failure in controlled experimentation differently from failure caused by poor management.

It also means recognising that capability takes time to mature.

There is often pressure in government programmes to demonstrate immediate progress. Training can be attractive because it produces a visible output: people attended a course, certificates were issued and a capability programme was completed.

But genuine capability development is less tidy.

People need opportunities to practise. Teams need time to establish new behaviours. Leaders need to reinforce those behaviours. Lessons need to be shared. Approaches need to be adapted as circumstances change.

The result may take months or years to become fully visible.

That does not make it less important. It makes it more strategic.

Make continuous development part of delivery

Digital capability cannot be treated as a project with a start and end date.

Technology changes. User expectations change. Government priorities change. Delivery methods evolve. New risks emerge around areas such as artificial intelligence, data, cyber security and automation.

A capability that is sufficient today may not be sufficient in three years.

Organisations therefore need mechanisms for continuous development.

Communities of practice are one practical approach. They give practitioners a place to share patterns, discuss difficult problems and learn from work happening elsewhere in the organisation.

Regular show and tells, peer reviews and internal case studies can have a similar effect. They turn delivery experience into organisational knowledge rather than allowing lessons to disappear when a project closes.

Career pathways also matter. People need to understand how they can develop their skills and progress within digital roles. This is particularly important for retaining experienced practitioners. If the only way to develop is to leave the organisation, capability will continually leak away.

There is also a role for reflective practice.

After a major discovery, alpha or service transition, teams should ask what they learned about the service, the users and their own way of working. The objective is not simply to produce a retrospective document. It is to make learning part of how the organisation operates.

For me, this is one of the most important shifts required.

The question should not simply be, “Did we deliver the project?”

It should also be, “Are we better at delivering this type of work now than we were before?”

If the answer is yes, the organisation has created something that lasts beyond the immediate programme.

“We initially brought the team in to help us address a specific delivery challenge, but the impact was much broader. They helped different parts of the organisation develop a shared understanding of the service, the users and the problems we were trying to solve. That changed the conversations we were having at senior level. We moved away from discussing individual requirements and technology solutions and towards thinking about outcomes, evidence and the capability we needed to deliver them. The most valuable thing they left us with was not a set of documents, but a team that was better equipped to continue the work.”

Director of Digital and Technology, Public Sector Organisation

Digital capability is an organisational asset

Government will continue to face pressure to modernise services while managing constrained budgets, legacy technology, complex policy requirements and increasing public expectations.

There is no single training programme that will solve those challenges.

The more sustainable approach is to treat people and capability as strategic assets.

That means investing in specialist skills while also developing digital confidence across the wider organisation. It means using real delivery as a learning environment. It means creating opportunities for practitioners to share knowledge and develop one another. And it means ensuring leadership, governance and organisational culture support the behaviours that modern digital delivery requires.

It also changes the role of external consultancies.

The best engagements should not simply provide additional capacity. They should help organisations develop their own capability, challenge established assumptions and leave teams better equipped to continue the work.

As a business analyst and service design practitioner, I see this as a central part of the role. Much of the value comes from helping people understand a problem differently, creating shared understanding across disciplines and giving teams practical ways to make better decisions.

The deliverable may be a service map, a set of requirements, a redesigned process or a new digital service.

But there is another deliverable that is just as important: the capability the team develops while creating it.

Government does not need organisations that are simply capable of delivering one successful transformation programme.

It needs organisations that become progressively better at understanding problems, working with users, making decisions and delivering change.

That requires sustained investment in people, skills and culture.

The question for digital leaders is therefore not simply whether their teams have received enough training.

It is whether the organisation has created the conditions for those skills to become capability — and whether that capability will still exist when the current programme is over.

What would change in your organisation if developing digital capability was treated as an outcome of every transformation programme, rather than an HR activity sitting alongside it?