Overview

A large government organisation wanted to extend the benefits of public-facing digital transformation to its internal technology programmes.

The ambition made sense. Public-facing digital services had benefited from clearer standards, stronger user research, better service design, and more disciplined delivery practices. But internal technology work was different. It included operational tools, support processes, procurement decisions, specialist teams, local workarounds, legacy systems, and smaller efforts that did not justify the full weight of a public-facing service governance model.

The work began by asking whether the governance model developed around the GDS Service Manual could be applied more broadly to internal technology change.

The manual provides guidance, standards, and delivery practices for building good government services. It had helped shape public-facing digital transformation, but applying the same governance weight to internal technology work was a different question.

The answer was not straightforward. The principles were valuable, but the process could not simply be copied.

Key challenges

Extending digital transformation to internal technology work presented several challenges:

• defining the scope of “internal digital” across a large and complex organisation
• understanding which parts of GDS-style governance were useful, and which would be too heavy
• identifying barriers and success factors across existing digital transformation efforts
• making better technology decisions without defaulting to large enterprise procurement habits
• supporting specialist edge cases without turning every small need into a major consultancy exercise
• developing a multi-year implementation and governance plan while still delivering useful evidence along the way

Outcome

The work produced a practical strategy for internal digital transformation, grounded in research, organisational analysis, and evidence from live internal technology efforts.

Research with digital leadership helped identify barriers and success factors for transformation across the organisation. Further work across mobile technology, field-worker procurement, digital support, and operations tested those findings against real decisions.

The key finding was that the GDS model could not simply be transferred to internal technology work. The governance weight was too high for smaller, faster-moving, or more specialist internal needs. What mattered was understanding why the model worked, then turning those lessons into operating principles that could scale across the organisation.

This provided evidence of organisational, operational, and individual skills transformation needs, along with a multi-year plan for implementation and governance.

The result was not a new framework for its own sake. It was a way to make internal technology change more user-centred, evidence-led, proportionate, and governable.

Challenges in depth

Translating public-facing digital governance into internal change

Public-facing digital transformation had created better ways of designing, building, and governing services. User research, service standards, agile delivery, and stronger digital leadership had all helped improve large public services.

The question was whether those same ideas could be applied to internal technology programmes. At first glance, the answer seemed obvious. Internal users are still users. Internal services still need to work. Technology decisions still need evidence, governance, and delivery discipline.

But internal technology change carries different pressures. The work ranges from large strategic programmes and enterprise-wide systems to small, local, or highly specialised operational needs. A governance approach that makes sense for a major public-facing service can easily overwhelm a smaller internal tool, procurement decision, or specialist team.

Digital principles still mattered. The challenge was applying them proportionately.

Solutions

The work began with research into barriers and success factors across digital transformation efforts.

Working with a researcher, we interviewed digital leadership and analysed internal technology activity across the organisation. The aim was to understand what kinds of work were actually happening, where transformation efforts were succeeding, where they were getting stuck, and what kind of governance would be useful at different levels of scale and risk.

The research showed that the GDS model could not simply be copied into internal technology work.

The cost and complexity of full-scale governance made sense for major public-facing services, where the risk of failure was high and the impact was visible. It did not make sense to apply the same model to every internal tool, procurement decision, operational improvement, or specialist team need.

The useful work was not creating a lighter version of the same bureaucracy. It was identifying the principles that made digital transformation work, then finding ways to make those principles usable inside the organisation.

Those principles included:

• starting with the people affected by the change
• focusing on measurable outcomes, not technology adoption
• communicating early with the right stakeholders
• managing uncertainty in the right amounts
• thinking beyond delivery into support, operations, skills, and long-term ownership

Governance alone couldn’t deliver the transformation. The organisation needed operating principles that helped people make better decisions in context.

Making better technology decisions through evidence

Enterprise technology decisions often happen too far away from the people who’ll live with the consequences.

New technology arrives with vendor ecosystems, feature lists, applications, development tooling, and long-term promises. Procurement processes are then asked to compare bids, specifications, and commercial terms. On paper, that can look rigorous. In practice, it can mean decisions are driven by what vendors are selling rather than what users and the organisation actually need.

That was the challenge. The organisation was being asked to make decisions about new technology using familiar procurement habits, where specifications and bids could carry more weight than user needs, support models, organisational readiness, or lifetime cost.

For internal digital work, this matters because the cost of a poor decision rarely appears at the point of purchase. It shows up later through support burden, workarounds, unused features, lost productivity, and operational drag.

The question was how to make technology decisions using evidence from real users and operating conditions, not just vendor propositions and procurement paperwork.

Solutions

The work focused on principles rather than frameworks.

Research showed that successful leaders were not always formal agile practitioners. What they shared was a set of internalised principles that helped them navigate change while still meeting strict governance requirements.

Those findings were then tested across live internal technology efforts and with people who had seen previous transformation programmes come and go. That mattered. In an organisation with a long memory, another set of abstract principles could easily become just another poster on the wall.

The principles had to be made useful in context:

• start with people, including internal users and operational teams
• deliver measurable change, not technology for its own sake
• communicate and engage early, especially with people who understand organisational history
• manage uncertainty without pretending it can be eliminated
• think beyond delivery into learning, operations, support, monitoring, and long-term use

The next step was to develop an education and adoption plan around them. Not training as a one-off course, but practical guidance backed by examples from the organisation’s own work, so leaders and teams could see what the principles looked like in real situations.

This made the work less about applying agile, and more about creating the conditions where agile ways of working could make sense.

The transformation was not surface change. It was helping the organisation understand what had to change around the technology for the technology to matter.

Avoiding surface-level agile change

Large organisations can adopt the language of agile without changing very much.

People go on courses. Project managers are renamed scrum masters. New ceremonies appear. Posters go on walls. But the deeper habits of management, governance, procurement, support, and decision-making remain largely unchanged.

In organisations with long memories, this can be worse than doing nothing. People have seen transformation efforts before. They know when a new language is being added on top of old behaviours.

That creates cynicism. It also creates a practical problem.

If agile or digital transformation is treated as a framework to be rolled out, the organisation can end up measuring whether it is “doing the thing” rather than whether anything useful has changed.

Solutions

The work focused on principles rather than frameworks.

Research showed that successful leaders were not always formal agile practitioners. What they shared was a set of internalised principles that helped them navigate change while still meeting strict governance requirements.

This mattered because internal technology change did not need another heavy methodology. It needed a way for leaders and teams to make better decisions in context.

The principles helped connect digital transformation to the reality of the organisation:

• start with people, including internal users and operational teams
• deliver measurable change, not technology for its own sake
• communicate and engage early, especially with people who understand organisational history
• manage uncertainty without pretending it can be eliminated
• think beyond delivery into learning, operations, support, monitoring, and long-term use

This made the work less about applying agile, and more about creating the conditions where agile ways of working could make sense.

The transformation was not surface change. It was helping the organisation understand what had to change around the technology for the technology to matter.

Building a multi-year path for internal digital change

Internal digital transformation could not be solved through one project, one procurement decision, or one new governance process.

The organisation needed a way to keep learning from internal efforts, turn those lessons into reusable guidance, and align with wider government standards without importing unnecessary bureaucracy.

That meant looking across live examples, not only at central strategy.

Mobile technology, specialist field-worker procurement, digital support, operations, service design standards, and digital skills all became evidence-producing efforts. Each one helped test the emerging strategy and show where organisational, operational, and individual skills needed to change.

The challenge was to create a plan that could guide a multi-year transformation while still delivering value through smaller, practical work.

Solutions

A multi-year implementation and governance plan was developed from the research and live evidence.

The plan identified transformation needs at several levels:

• organisational — how internal technology work should be governed and prioritised
• operational — how support, procurement, delivery, and service ownership needed to change
• individual — what skills, behaviours, and leadership capabilities were needed
• governance — how to make oversight proportionate to risk, scale, and impact

The work also reviewed and aligned with wider government efforts, including Cabinet Office work on service design standards and digital technology skills.

This helped ensure the internal digital strategy was not isolated from broader government direction, while still being grounded in the organisation’s own context.

The result was a practical route for scaling digital principles internally without applying the same governance weight to every type of work.

Principles, not frameworks

The main finding was simple: the organisation could not copy the GDS model wholesale into internal technology change.

The governance model was too heavy for many internal efforts, especially smaller, specialist, or operationally specific pieces of work. But the principles behind successful digital transformation were still valuable.

The work showed that internal digital transformation needed to be user-centred, evidence-led, proportionate, and grounded in organisational reality. It needed to help teams make better decisions, not force every decision through the same process.

That meant focusing less on whether the organisation was “doing agile” and more on whether it had the leadership, evidence, governance, and operating practices needed to change well.

The transformation was from framework adoption to principle-led change. Not another set of posters on the wall, but a practical way to extend digital transformation into the internal work that keeps a large organisation running.