The core problem in local government digital is capacity

This is the content of the ‘article’ element of the email newsletter I sent last week. Publishing here for posterity.


2025 has been a pretty tumultuous year in local government digital, largely due to the impact of the Localism bill in late 2024 and the imminent (and indeed immanent) prospect of local government reorganisation. Following the latest cabinet reshuffle, it feels like the ambitions might be being dialled back a little (note: I have no special insight other than what I read online), which probably isn’t a bad thing.
I can’t help but feel that some kind of coming together is required if the sector is to get the most out of the digital opportunity. I’ve been lucky enough to be involved in several research projects in the last year looking at some of the the big picture stuff, and to me the issue of capacity seems to be screaming out as the fundamental issue facing council digital teams across the country.
  • Local government software is largely terrible because nobody has the time to put the effort into demanding and buying something better.
  • Local government data is in a poorly maintained mess because nobody has the time to sort it out.
  • Local government websites are still full of unintelligible content and PDF forms because nobody has the time to get round to fixing it.
I could go on (but don’t have the time, LOL!) but you get my point – many of the oft-cited root causes of digital incompetence actually have a root cause themselves – capacity.
Have hundreds of councils trying to do the same thing, over and over again, is nuts, and there could have been some potential in using the LGR process to create some scalable teams to deal with the issue. Trouble is, LGR itself creates so much work that I dare say the opportunity wouldn’t be realised for some time.
I wrote a thing last autumn about how councils could start sharing digital, data, and technology capabilities in a way that doesn’t impact local policy setting or require huge sector-wide reform projects. Shared services have a bad rep in the sector, but it doesn’t have to be that way if we do things properly and take our time.
If LGR doesn’t end up happening as widely as once was expected, it would be nice to think that some of the conversations that have started up between digital people could still result in sharing capabilities, reducing burdens, and increasing capacity across the sector.

📅 Daily Note: September 18, 2025

Giles Turnbull: The strategy is enquiry

What I’m suggesting is a new approach for the times when there’s a perceived need for a document called a “strategy”. It shouldn’t be a document full of “we will”; it should be a website full of “what we’re learning”.

Use it to demonstrate your institutional capability to test and learn, to enquire and be curious.

# – micropost 23041


Key learnings from GOV.UK One Login discovery research for local government:

Key themes emerging from the research include:

  • cost savings are essential – councils told us this would be critical to secure leadership buy-in
  • identity verification is a USP – councils value secure verification and the potential to share credentials across local and central government
  • suppliers are open to integration – many are already using, or moving towards, OpenID Connect (OIDC) compatibility
  • forward thinking but stretched – councils want to future-proof systems, but limited resources, capability, and competing priorities are barriers
  • user adoption risks – concerns about digital exclusion, resident trust, and the transitioning of users to a new system

# – micropost 23043


Dave Winer, It’s really simple:

FeedLand is the perfect back-end for a twitter-like system, for the feeds part. And for the words, the perfect back-end is WordPress. I only discovered that about 1.5 years ago. And I had to see what it looks like. No more tiny little text boxes, it’s a real editor that supports all the features of the web. How do I know? Because it saves its data in Markdown. That has come to be the defining format for the text-based web. One which has been totally ignored by the twitter-like systems. How could they miss that? Markdown is like MP3. If you’re mixing sound into feeds you use MP3 of course. It’s there for you to use. As was Markdown. If you’re mixing text you’re mixing Markdown.

# – micropost 23045


Really Simple Licensing – “The open content licensing standard for the AI-first Internet”.

RSL is an open standard that lets publishers define machine-readable licensing terms for their content, including attribution, pay per crawl, and pay per inference compensation.

# – micropost 23046


Avoiding the hidden costs of leadership debt – Oli Lovell, Public Digital:

Technical debt is well recognised. But the same logic of ever-shifting organisational needs – and therefore the debt accrued by standing still – applies to leadership too. As a leader, your skills, models and culture operate as a system of their own, determining how well your organisation is able to adapt and respond to change.

# – micropost 23048


Decision making at the right level with Hats, Haircuts and Tattoos by Emily Webber:

What I like about these definitions is that they provide a framework for considering a decision, while also allowing for the differences and nuances of the situation and the experience of the people making them.

# – micropost 23049


This is a fair challenge:

i know its a lot easier to book the same recurring slot every fortnight / month

but its quite depressing seeing group after group you never get to attend, because they always meet on your non working day 😔

I did the lazy thing with Localise Live! but probably should have mixed it up a bit more. I will be making recordings available to people who sign up, so maybe I need to make it clearer that people should sign up even if they can’t make the meetings, so they get that access…

# – micropost 23050


David Gerrard – UK government productivity not enhanced by Copilot AI

The main uses were “transcribing or summarising a meeting”, “writing an email”, and “summarising written communications”.

The bot didn’t do so well on anything more complicated. Users could churn out PowerPoint slides faster, but worse. Excel data analysis was slower, and worse.

# – micropost 23051


How Tim Cook sold out Steve Jobs by Anil Dash:

There’s a tech industry habit of second-guessing “what would Steve Jobs have done” ever since he passed away, and most of the things people attribute to him seem like guesses about a guy who was very hard to predict and often inconsistent. But recently, we have one of those very rare cases where we know exactly what Steve Jobs would not have done. Tim Cook and Apple’s leadership team have sold out the very American opportunity that made Steve Jobs’ life and accomplishments possible, while betraying his famously contemptuous attitude towards bullshit institutions.

# – micropost 23052


James Plunkett writes What does digital-era healthcare really mean?

When the UK government published its 10 Year Plan for Health two months ago, there was general support for its direction of travel: shifting from analogue to digital, from hospitals to communities, and from treatment to prevention.

The question people asked is whether the healthcare system has the capability to deliver these shifts. Or, put more bluntly, ‘we’ve heard this all before, so why is this time different?’

# – micropost 23054


📅 Daily Note: September 3, 2025

Brent’s Innovation Journey: Building a ‘Base’ for Local Government Innovation by Ryan Hamilton on the LOTI blog:

At Brent, we’ve been trying to rethink how we tackle problems in a way that makes ‘innovation’ not just a buzzword, but a practical, everyday reality in local government.

That journey led us to something exciting: We will soon be launching ‘The Base’ , a dedicated space at the Civic Centre (both physical and cultural) where bold ideas, agile working and collaborative experimentation come to life.

# – micropost 23005


What makes a good outcome? by Jamie Arnold:

In the world of digital and organisational change, being able to define and communicate a strong outcome is a leadership superpower. Whether you’re working on a product, service, or internal shift, a well-crafted outcome sets direction, aligns teams, and builds momentum. Here’s how to make your outcomes truly effective.

# – micropost 23006


New book to improve accessibility of Welsh digital public services – from the Centre for Digital Public Services.

# – micropost 23007


# – micropost 23008


I like the idea of “digital everywhere” – amongst a whole range of brilliant ideas and reflections from Catherine Howe:

Digital everywhere: The embedding of digital practitioners within services alongside a digital skills development program is something I feel we’ve tested in a limited way but clearly it works when done right and I’m really looking forward to having the capacity to develop this approach. This requires a really strong approach to making sure those digital roles are properly designed and also wired into the core digital team as well as clear guide rails that need to be context sensitive.

# – micropost 23009


# – micropost 23011


Product strategy, prioritisation frameworks and responding to change by Alan Wright:

Product teams often face more opportunities than they can act on, with new ones arising all the time. This post explores the link between strategy and priorities, when prioritisation frameworks help or hinder, and how to empower teams to make smart, timely decisions as new opportunities emerge.

# – micropost 23012


From Strategy to Strolls: A Few Weeks of Progress and Pauses, by Atika:

One of the standout achievements in the last few weeks was securing approval for our new strategic framework and governance model. This marks a significant step forward in aligning our digital ambitions with the Council’s broader priorities. The framework, shaped through collaboration and challenge, is now the backbone of how we’ll deliver impact—anchored in transparency, agility, and accountability. We’re also making good progress on the TOM work to make sure we have the culture and capability to deliver this.

# – micropost 23013


The courage to digitally transform with the Digital Layer and AI – interesting talk from Mark Thompson.

 

# – micropost 23019


📅 Daily Note: August 7, 2025

AI in Adult Social Care – guidance for adult care providers on the use of AI.

# – micropost 22995


Giles shares “examples and links about working in the open and agile communication”.

# – micropost 22996


# – micropost 22997


Service mapping: building transparency, trust and transformation together on the Public Digital blog.

Service maps aren’t just tools – they’re catalysts for transformation. They clarify complexity, foster collaboration and enable informed decision-making. They help organisations navigate the challenges of transforming and continuously improving their services. We worked with Defra’s Farming and Countryside Programme (FCP) to develop a service map and a set of service outcomes.

# – micropost 22998


Blood, Sweat and Roadmaps by Maarten Dalmijn:

Your roadmap is like an indicator species that reveals all the organizational dysfunctions in your organization. The roadmap is where business and tech meet, where your vision and strategy collide with your execution and teams. The roadmap is where departments and business units compete with your teams and other organizational priorities.

via Steve.

# – micropost 22999


Steve Messer: Don’t just keep the lights on, shine bright:

Platform products, built by government for public sector organisations, are intended to be better, cheaper and preferable to competitors. If an arms-length body or small government organisation has to choose between a private-sector platform or a platform built by government, both of those platforms are in a market. The arms-length body will choose which platform to use based on the features offered, the price, the complexity of integration, design, accessibility, and loads of other factors.

# – micropost 23001


Alan Wright – Jobs to be Done surveys:

As a product manager, one of my favourite ways to prioritise problems to solve for users is to understand their Jobs to be Done (JTBD). The best way to get this data is by having conversations with many users, but this is not always something users have time for. Surveys are a great complimentary method to gather this data quantitatively and quickly. In this post, I share the thinking behind the Jobs to be Done survey I have been running with users in my current role.

# – micropost 23002