Digital Transformation at Scale summary

One of the first challenges digital teams face in big organizations is pressure to fix everything at once. The problems are piling up, the system is creaking, and people expect instant solutions. But trying to solve everything immediately is a trap. A better approach is to start with something small and useful – and make it work really well.

When the GDS got going, it was surrounded by major IT disasters and long-running policy failures. It would have been easy to get drawn into those. But instead, the team focused on showing they could deliver one thing, fast, that users would actually notice. That early example was the alpha version of GOV.UK – a prototype built in just 13 weeks. It replaced a chaotic patchwork of government websites with one clean, functional site. It wasn’t perfect, but it worked. And that mattered more than anything else.

New digital teams often face a lot of internal attention before they’ve had a chance to build anything. Leaders want announcements, media teams want headlines, and departments want their priorities on the roadmap. The safest move is often the least exciting one: keep your head down and get something working before stepping into the spotlight.

Holding off on publicity gave the GDS space to build trust. Its early successes – like shipping the GOV.UK prototype and the e-petitions site – were delivered without fanfare. This was deliberate. Avoiding a big launch helped the team avoid becoming a target before they had anything to show. It also meant that when they did go public, they had proof of delivery, not just promises. Inside government, where flashy initiatives often disappear without results, that counted for a lot.

Once a digital team starts delivering real services, everything shifts. People inside the organization begin paying closer attention – not just to what’s being said, but to what’s actually being built. And at this point, credibility becomes the team’s most valuable resource. Not branding, not vision decks, but working services that users can see and use.

This is also the moment where many well-meaning efforts stall. A lot of teams get caught in what looks like innovation but never reaches users. There’s a difference between running workshops and actually replacing a clunky service with something faster and clearer. What matters now is follow-through. Prototypes and experiments are useful, but they have to lead somewhere real. That’s how digital teams earn permission to do more.

After early wins, digital teams often face a tougher question: can they influence how the rest of the organization works. It’s one thing to launch a new service. It’s another to stop bad ones from being built. And that’s where real authority starts to matter.

Most large institutions are full of legacy systems and expensive contracts that run on autopilot. Changing that means shifting power. For the GDS, that shift began with a clear mandate to review digital spending across departments. After demonstrating success with early services, the team made a direct appeal to top ministers for more control. They asked for the right to challenge big IT decisions – and they got it.

Many digital teams begin by focusing on what’s broken or outdated. But the more effective strategy is to start with what’s big. That means looking for services with the highest user demand or the greatest cost to deliver – because that’s where even small improvements make the biggest difference.

The GDS didn’t just rely on gut feeling to decide what to work on. It created a tool called the Transactions Explorer, which tracked data on hundreds of government services. It showed how many people used each service, how much it cost to process, and how many steps it took to complete. With that information, the team could see at a glance which services were ripe for redesign. One example was registering to vote – a high-volume task with a clunky process. By rethinking it from the ground up, the team built a simple digital service that millions of people could use easily in just a few minutes.

Delivering great digital services is only the first step. What comes next is harder. Once the early wins are in place and the most visible fixes are done, the real challenge is making change stick. That means shifting the deeper structures – things like funding models, performance frameworks, and the way risk is managed. Without that, even the best digital teams can burn out or stall.

The GDS faced this exact moment. After building a strong track record, the team started to run into barriers that weren’t technical at all. Some departments still relied on decades-old procurement contracts. Budget decisions were made on annual cycles that didn’t match how digital products evolved. Success was measured by compliance and delivery of fixed outputs, not whether users could actually get what they needed. These problems required new ways of thinking about accountability, control, and value.