Wednesday, 22 April, 2026

Guidance from the ICO on AI and freedom of information requests:

Information requests often involve secondary correspondence, such as clarification or internal reviews. If requesters use AI to read and respond, it can result in long, complex emails. These take valuable time for practitioners to process and understand.

We appreciate that resources are already stretched for many organisations. This guidance is intended to reassure practitioners that the Freedom of Information Act (FOIA) can accommodate requesters who use developing technology. The existing FOI principles are generally capable of dealing with the impact of AI being used increasingly in this area.

#

A fun long-ish read from the makers of the iA writer app on Europe’s desire to move away from Microsoft Office and what it might take:

Severance illustrates something so familiar that it’s hard both to recognize and hard to ignore: Fluorescent light. Endless hallways. Ritualized procedures. People performing point-and-click tasks on screens whose purpose they cannot fully explain. And everyone behaves as if the system were natural. It’s both weirdly old and claustrophobically on brand. Sounds familiar? Severance beautifully illustrates how it feels using Microsoft Office all day long, in 2026.

At Lumon, they circle and click numbers whose meaning they cannot see. In Office, we click and circle numbers whose basis we hardly question. A spreadsheet cell feels objective. A chart feels authoritative. The grid replaces doubt. The format replaces understanding. The brand identity makes it right.

#

Jens Gemmel shares a substantial post with some really good, interesting in depth thinking around the potential for LGR to be used as a level for wider, system level change (LinkedIn warning):

When we are talking about Sussex LGR, what we are seeing on the surface is a discussion about geography, governance and structure, shaped by ministerial direction and the emerging preference for a two-unitary model. Those discussions provide direction, they create a framework for decision-making and they bring a level of clarity to what is otherwise a complex and evolving landscape.

Yet underneath that surface sits something far more consequential, because what is taking shape is not simply a reorganisation of councils, but a reconfiguration of an entire system that connects services, people, data, infrastructure and value across place. The decisions being made now will determine how that system behaves, how demand flows through it, how pressure builds or is prevented, and how effectively Sussex is able to respond to the needs of its residents over the long term.

I don’t disagree with what Jens says. I’m cautious about whether the timing is right – LGR feels like a crunch time where every spare scrap of resource is going to be spent on just keeping the wheels on the road.

Perhaps these ideas will be revisited once the dust has settled – although that would be a missed opportunity. Using a time of change to change in the right way seems an obvious thing to do – but people are going to be so stretched, I’m not sure it will be possible.

#

The latest resource in the Local Government Reorganisation Digital and Cyber Playbook has been published – Digital and cyber leadership during transition:

Research by the Local Government Association (LGA) is clear that strong, early and visible leadership is one of the biggest success factors for local government reorganisation (LGR). A lack of leadership represents a clear risk to delivery.

LGR places significant demands on digital and cyber leadership. New organisations must operate safely from day one, while at the same time planning for several years of transformation.

#

I’ve been playing around a bit with Gitbook to see if it would be a good fit for a publishing itch I need to scratch. I ended up tearing my (somewhat limited) hair out over it – I don’t think I’ve ever used a technology so wilfully obscure!

What I really wanted was a means of writing markdown documents on my laptop, which with as little fuss as possible I could publish as simple webpages.

In the end I went with Obsidian Publish. I don’t really mind what editor I use, and Obsidian is easy enough to configure to look and feel how I like it. What’s most important is that publishing the content is a simple case of clicking a couple of buttons.

The results are a nice, simple set of pages with a structured table of contents on the left hand side – perfect.

It does cost a few quid a month, but I figured it’s worth it for the convenience.

#

Tuesday, 21 April, 2026

Lovely story in the Guardian about the making of the 8-bit classic game Chukie Egg:

The iconic game that came to define 8-bit programming still conjures flutters of nostalgia 40 years on – all thanks to a 15-year-old tea boy who worked a Saturday shift in a computer shop in Greater Manchester.

Can remember spending many a lunchtime at school, hunched over a BBC Micro playing this game!

#

Monday, 20 April, 2026

Useful reminder from dxw about the potential for things to go wrong on WordPress sites – in this case, a change of ownership for a suite of plugins.

In August 2025 the new owner planted a backdoor in the purchased plugins and in 5–6 April 2026 the backdoor was weaponised, by planting malware in sites that had the plugins installed. On 7 April the WordPress Plugins Team permanently closed all essentialplugin plugins, and on 8 April, the day we opened the incident at dxw, WordPress pushed an update to the plugins which removed the malicious code.

Of course, things can go wrong with any technology platform and the key is staying vigilant. Sounds like the whole WordPress community mobilised pretty quickly to shut the threat down.

#

Saturday, 18 April, 2026

Like most people, I don’t often need to interact with my local council, and so – given the way I make a living – I tend to take notice when I do.

Recently we got an email with an invoice on it from the council to renew our garden waste bin subscription. I remember that when I ordered it originally I had open an account on the council website, so I went to log into that to process the renewal.

Of course, having clicked to login to my account, I was then asked which my account I wanted – the one for council tax or the one for everything else. I chose everything else and once I had reset my password, logged in.

On logging in, the only thing I could do was order another garden waste bin. My account did not know that I had one.

Instead, to pay the invoice, I had to leave the my account section, go to ‘make a payment’ and enter the details (account number, invoice number, my address, even my email address) from the invoice manually to pay by card.

To avoid this in future, I would need to phone the council – no options to set up a garden waste direct debit online, whether on my account or not.

Just this simple, highly transactional, example shows how far we still have to go. This isn’t a complex service like social care or SEND or housing. Despite having the technology for an account, doing simple things with it are still not possible.

It’s pretty pathetic.

#

Friday, 17 April, 2026

The National Digital Exchange is a really neat idea that is looking more and more impressive.

Basically, it’s a way to try out local government software – often open source – without needing to buy it first or run costly proof of concept projects.

Effectively, you choose a tool and then it is automagically spun up for you in a temporary bit of Amazon cloud.

Some of the tools available to try include:

  • LocalGovDrupal
  • Back Office Planning System
  • FixMyStreet
  • LocalGov Income Management System
  • Simply Readable (AI-powered document translation)

It’s a brilliant idea and a great way to showcase open source solutions for the sector.

#

Thursday, 16 April, 2026

Will Callaghan is on a bit of a blogging roll at the moment. Here he is on Kickstarting collaboration during LGR:

Of the speakers, the stand out two for me were Kate Hurr and Madeline Hoskin, of Cumberland and North Yorkshire Councils respectively. They’ve both been through LGR relatively recently, and shared practical hard won advice.

Both argue that councils need to collaborate more, particularly through LGR. We’re all meeting the same needs, there’s very little about our organisations that is unique. I totally agree. The questions for me are: what barriers exist to collaboration over the next few years, and how can we remove them?

#

Wednesday, 15 April, 2026

I had the thought the other day that an awful lot of time gets wasted in local government digital because of the constant cycle of probably unnecessary change.

Here’s an example: new chief digital person comes in, and the first thing they want to do is to impose themselves, so new strategy, often new tech, new approaches and ways of working etc.

Now obviously everyone feels justified in doing this. Frankly, if I were to get a new job running digital in a council, it’s the first thing I would do!

But it is usually a waste of time. I heard the other day about a council who have brought in a new interim CDO type person and the first thing they are doing is to get rid of one digital platform to replace it with another. It just so happens to be the one that was previously canned to make way for the current one!

Put like that, it seems very silly, and a lot of work and time for no real obvious improvement. After all, a team might spend 18 months or 2 years migrating from one platform to another, to be in basically the same position as before, only on different tech.

Trying to put a stop to it, though, is really challenging. Perhaps this is, again, an argument for a bit less local autonomy in individual councils when it comes to choosing technology. If all the time, energy and money spent on cycling through different options every 5 years was instead invested in improving shared platforms, we probably would make a lot more progress.

#

Tuesday, 14 April, 2026

GDS Local have published the first iteration of their architecture for (digital) local government.

It looks at this stage like very high level, simplified enterprise architecture.

It will be interesting to see where it goes next. I worry about architecture being done for its own sake, and so understanding what the outcome this will help achieve is going to be key.

Phil’s accompanying blog post helps with some of that:

It makes it easier to describe applications, integrations, data and underlying capabilities, regardless of which products are in use. That supports clearer conversations with suppliers, internal governance groups, and central government. It also makes dependencies and risks easier to see.

For me there are two pragmatic outcomes that make sense here.

One develops the shared language thing further, translating between technology design and service design, so conversations can be had by both sides with everyone understanding what the others are referring to.

I think that probably lies in connecting this kind of technology architecture with service patterns, such as those being worked on in Wales.

Secondly, I wonder if the nailing down of a common language and definitions of what digital gubbins councils need to deliver their services might lead to interesting conversations about the delivery of that gubbins, and where capacity could be created in the sector by sharing a lot of the stuff that doesn’t really matter to most people. More on that in this post from ages ago.

#

Am super impressed with the way Doug is using AI tools to help him build useful software. Commonplace is a way of saving online stuff into collections. It’s a bit like Delicious of old.

What’s more, browsing through the collections others have created, I have already found a few useful things I wouldn’t have seen otherwise: Heynote, a simple ‘scratchpad’ style text editor; and Joplin, an open source everything-bucket like Evernote or my current choice DEVONthink.

#

Monday, 13 April, 2026

I sent out a newsletter for the first time in ages today. It’s a simple dump of the last week’s blog posts from here.

Since I put in place the Jetopack-driven email subscription feature, precisely one person signed up, so it didn’t feel like the right way to do things. I’ll be disabling that shortly.

For some reason, people like a proper newsletter! I have a decent enough list of email addresses on the old Daveslist newsletter, which I used for this new blog based format. Will see what people make of it!

If you aren’t signed up, you can do so.

#

Richard Pope: Stop searching for AI ‘use-cases’. Design AI into services:

The principles of what makes a well-designed service remain the same as in the pre-AI digital era. AI should be treated as a design material rather than as a product in its own right. The goal of introducing AI into services should not be to create new “AI services”, but to make services work better for users.

#

Not come across LOTI’s service innovation cards before, but they are lovely and would be really interested to learn about how it plays out in a workshop setting.

It reminds me somewhat of the good old days of the social media and digital engagement games (that post is full of broken links, apologies, but I think you can get the drift) that David Wilcox, Steph Gray, and I used to run. I have often thought about what a digital transformation version might look like, and I suspect it isn’t a million miles away from what Eddie and the team have done here.

#

The Local Digital team at MHCLG is running a webinar to talk about the playbook we have been developing which guides digital teams through what they need to do during the creation of the new unitary councils.

It’s on April 29th at 10am and you can sign up on Eventbrite!

#

Friday, 10 April, 2026

Interesting perspective on Ai generated software from Quentin Stafford-Fraser:

As we enter an era where software development is much cheaper and easier, the number of people able to create their own bespoke apps will increase rapidly. Either you’ll do it, or you’ll pay your neighbour’s son a modest amount to do it for you. Good and/or important software, to be used by large numbers of people, will still require experienced developers, though they may spend more time guiding the AI than actually typing the code. But software that is good enough for you to use yourself? That’s becoming a different story.

If I could get my head around how it is done, I could spend the rest of my days perfecting a native Mac app that combined my favourite features from Netnewswire, Marsedit, DEVONthink, Ulysses etc etc.

#

Thursday, 9 April, 2026

Cloudflare have released a new open source CMS, that they are billing as the “spiritual successor” to WordPress.

Unsurprisingly, Matt Mullenweg has views:

The UI is in the uncanny valley of being sorta-WordPress sorta-not. I know it wasn’t a weekend vibecode project, but it has some of that smell.

I agree – having played with the sandbox version, it definitely feels like the result of someone typing “make me a wordpress clone” into Claude or something.

#