LGR and getting the new council website right
30 Jul 2025I’ve had versions of this post lurking in a drafts folder since 2021. Now that local government reorganisation is centre stage it might be helpful to share some reflections on my experience in Buckinghamshire back in 2019 and 2020.
a blog is your brain, over time, on the internet. Giles Turnbull
I insisted we talk about the work openly. That’s the only way it’s possible to write this post now, by re-reading dozens of weeknotes and watching back livestreams we hosted on YouTube (with a jerry-rigged camcorder, a macbook and OBS - this was just before the pandemic, so no universal video conferencing platform for staff).
Make the argument
We were changing from five organisations into one. I was not the only person with an opinion about the new council’s digital services. I was the first person to articulate an approach in a slide deck and start pitching it to the decision makers.
The strategy was simple - use the new website as a trojan horse for user centred design, demonstrate how to get things done with agile teams, introduce open source tech and open ways of working.
Local Government re-organisation brings bigger problems to solve than building websites, but not many are as visible or will be accessed by so many residents.
My pitch centred on:
- consolidating all websites onto one trusted domain
- providing coherent services that are easy to discover and use
- making local government participative, open and accountable
- communicating with authority and trust
- making great digital and user-centred publishing easy
- delivery by an agile team who work in the open
Get close to the LGR delivery team
Landing safe and legal new councils on vesting day will be a clear and consistent message. There will be teams of people, led by a programme director and they’ll mostly be working in waterfall and Prince2 project management methods.
Running agile teams in waterfall programmes can be a recipe for trouble. Agree the outcomes you’re working to and help people see how governance is built into every step. It’s difficult to do this in abstract during the set up phase, but demoing working software at the end of the first sprint helps give senior people the assurance they need. Follow this with an early private beta well ahead of vesting day and you can give your colleagues one less thing to worry about.
Agile accepts that the scope of the project will change over time. I can absolutely guarantee that will happen during LGR. Requirements changed, the scope changed, the budget changed. We had the new site live weeks ahead of time and avoided any big bang release.
Build a multi-disciplinary team
The uncertainty about future organisation design will make this difficult. I created a centralised digital delivery team with colleagues from across the five councils, before any decisions about future structures had been made. This might require spending some political capital and relying on people’s good nature.
This team was then augmented with specialists from digital and design agencies, whose support was tapered off after the new council was born.
However well things go, you’re very unlikely to be switching off all the old websites on vesting day. Having folks in the team who understand the new and the old is pretty critical.
Use LocalGov Drupal
I’m not one for particularly strong opinions on the internet. Content management systems are a solved problem and you have lots of choice in both open source and proprietary technology. Lots of them are very good. Lots of them will be fine for building new unitary council websites.
Back in 2019 I made the case for technology with a bias towards openness and speed of change. In a period of massive change we wanted to be the most flexible piece of the puzzle. This meant open source technology and complete control over what got built. Wagtail (an open source python based platform) was being used in the NHS and suited our needs. The nascent LocalGov Drupal project was kicking off its discovery. Wagtail was the right choice at the time and is an excellent platform.
With 60 councils using LocalGov Drupal and collaborating to improve outcomes and save money, it’s the right choice today. I would love to see more examples of public money funding public code in Local Government.
Get a head start on content
Between the five councils we had an incredible amount of content in pretty variable shape. Write down your content strategy (or steal this one from Essex ) and get a content audit started early. The GOV.UK style guide is there to use and LocalGov Drupal has you covered with content types.
Establish clear governance and set very high standards. You’ve got a great opportunity to get strict control over publishing - start with a small centralised team. You will get some pushback. Clear, structure and helpful content is in everyone’s interest - even the AI bots.
Work in the open
The best digital teams in government work in the open. They don’t just share code, they also share their thinking, research, designs and things that didn’t go to plan.
It’s low cost and makes for better project management. Publish a weeknote, host show & tells, write longer blog posts. It will give your stakeholders a constant drip feed of information and let people flag issues early. People will spot dependancies and identify risks you’ve missed.
You’ll be making something that lives on the open internet. Decisions about how it’s funded will be published in council meeting minutes. Use this opportunity to take the next step and purposefully write and talk about the work. Get a copy of the Agile Comms Handbook to guide the way.