A blueprint for modern digital government

In January 2025, GDS & DSIT published A blueprint for modern digital government, a 6 point plan for digital reform.

It’s fantastic. It’s also very long, and you have much to do. Here are 3 of the 33 “priority reforms” that stand out, ordered from the achievable to the transformative.

If you like to skim, I’ve collated the list of just the 33 reforms as a separate post.

Despite it’s length the blueprint is surprisingly coherent, tackling the problem from many angles. Channelling Wardley, if we begin the publicly visible part, the GOV.UK app, and trace it’s dependencies we can start to see how the reforms serve to reinforce each other.

The GOV.UK App

In the blueprints own words, the government will:

Introduce a Digital Wallet to store government credentials, and require services to issue a digital verified credential alongside any paper/card based credential or proof of entitlement eligibility by the end of 2027. — Blueprint: Point 1. Join up public sector services

…but this doesn’t give the full story. The launch event video goes into more detail: the Digital Wallet will be rolled out as a feature of the new GOV.UK app. [source]. It also offers a bold statement of intent:

“We are going to transform the relationship between citizen and the state.” — Rt Hon Peter Kyle MP

Why an app, why now?

The app aims to provide the visible value to us, the users. If it’s useful it will give legitimacy to the other policy goals.

The justification given in the launch video is that todays’ 18 year olds (newly minted voting citizens) were born in 2007, the same year the iPhone was launched (😱). It is reasonable to assume that, to them, apps are the default. It’s how we do everything from banking to socialising already. And GDS doesn’t assume. Point 1 of the Service Standard is “Understand users and their needs” by doing the user research.

From the private sector point of view, offering an app is the UK skating to where the puck has been sitting for the last 10 years. But there is a proper order of events to nation-scale digital transformation, and you don’t get to skip web day.

A small app on a huge web platform

The solid foundations of the GOV.UK web platform is exactly why Peter Kyle can promise that the 6 month old app will be ready for public use by June this year.

The android app is a thin wrapper around the existing website; like a personalisable version of the https://gov.uk home page.

The search feature is using a gov.uk API to do the work of fetching search results. It’s open source and published on github, so let’s take a look.

# Be Neo and see past the code. We're going to pick some words out, nothing more. Hold on.

object SearchConfig {
    const val BASE_URL = "https://www.gov.uk"
    const val API_BASE_URL = "https://search.publishing.service.gov.uk"
    const val SEARCH_PATH = "/v0_1/search.json"

Source: github.com/alphagov/govuk-mobile-android-app

This tells us the current version of the app pulls search results from an API at:

You can click that link and try it. The response won’t be pretty but it will be data that you (or an app) can use:

  "results": [{
      "title": "Sign in to your Universal Credit account",
      "link": "/sign-in-universal-credit",

The title for the first search result is “Sign in to your Universal Credit account” which is text the app will show for this search result and the link is /sign-in-universal-credit.

If you select that item, it will open the https://gov.uk/sign-in-universal-credit web page as a view in the app, just as you would see it in your mobile web browser.

There is work to do to make this feel seamless, but the point is that the app gets a huge speed boost by reusing the web platform and the Design System that allows the app builders to add new features that match the gov.uk web pages.

This saves years of work. The task is not “rebuild all 700,000 web pages as features of the app”, but instead “do the work that makes apps interesting”.

Just moving the gov.uk homepage into an app could have been a hard sell but following the growth-hacking, value-propositioning playbook, they are launching with a killer app exciting initial use-case: a digital drivers license. It will include an eKYC feature that will let you prove that you are, for example, old enough to buy fireworks and alcohol without having to also share the other details on your license, like the address of that party.

Screenshot showing how to prove you're old enough to buy fireworks using the GOV.UK Wallet

The alpha/beta release pattern card is ticked too! Before it’s rolled out across the country, 250,000 UK Veterans will get access to the digital wallet feature to make it easier to access their veteran card and the benefits it offers. Just pause and admire that framing for a second. Honouring heros with early access and also finding a beta test group of the right scale that may also be more willing than average to report back on their early adopter experiences.

And they stick the landing, with a clear statement that it will be available by the end of 2025.

APIs Everywhere

Mandate the publication of a standard set of APIs and events by public sector organisations. Starting with an expectation that every new service in central government departments will have an open API. — Blueprint: Point 3. Strengthen and extend our digital and data public infrastructure

Apps use APIs to get things done. The gov.uk app needs departments to offer APIs so it can connect users with the service they provide. In return The app will give the new APIs an in-house customer that can provide early feedback. Meanwhile, reframing departments around open, documented APIs nudges them towards digital-first and service-first delivery. Hey, it worked for Amazon.

To calibrate how significant a change “APIs for everything” could be at this point in 2025, it’s worth noting that the current Disability Living Allowance form is 40 pages long, emotionally draining, and still paper-only. There is no option to fill it out online. You have to post that physical bundle to a doctor, who may or may not post it back with their part completed, before you get to post it to the DWP and wait for at least 17 weeks for the verdict.

Digital transformation represents an opportunity to redesign government around providing services that work well for the users who need it most. The section in the blueprint that proposes a performance metric around reducing the ‘time tax’ of public services will hopefully focus the effort where it is most needed.

Modern digital government should reduce the ‘time tax’ on people using public services. Not just the time it takes to use a service, but the time to understand what needs to be done. — Blueprint: What we want to deliver

Fixing funding

…OK But what about treacherous operating conditions for running digital projects in a government setting?

Just last week Mike Bracken reminded us that HM Treasury’s process still strongly favours large up-front capital expense projects with a 3 to 5 year plan they can do the cost-benefit analysis on, and is completely at odds with the need to quickly spin up small teams for test-and-learn digital projects that may last months, or if successful, require on-going revenue funding.

This mismatch either kills agile projects before they start or forces them to role-play a waterfall project and pretend they can predict what they will need in 3 years time before they’ve even started talking to users.

They want to fix that too!

The digital centre will work with HM Treasury to reform the government’s funding approach…

Launch tailored funding models for digital products and services, legacy remediation and risk reduction, and staged, agile funding that better enables exploratory work with new technologies. — Blueprint: Point 5. Fund for outcomes, procure for growth and innovation

And more…

The promise of ‘digital ready’ legislation, a line about trialing a new unique identifier on children that would benefit from more context …there really is something for everyone. I encourage you to give the blueprint a read.

Thoughts? Hurl them at https://bsky.app/profile/olizilla.bsky.social