Tuesday, 2 September, 2025

Holibobs

Am back from a wonderful week with the family in Suffolk. Some lovely days by the sea in Southwold and Aldeburgh, and a trip to the castle in Framlingham too.

Thursday, 7 August, 2025

📅 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

Friday, 25 July, 2025

📅 Daily Note: July 25, 2025

I *thought* I had settled on Devonthink as my everything bucket, but now I am falling down an Obsidian shaped rabbit hole thanks to Steve Messer linking to this monster:

Every few months I set aside time for a “random revisit”. I use the random note hotkey to quickly travel randomly through my vault. I often use the local graph at shallow depth to see related notes. This helps me revisit old ideas, create missing links, and find inspiration in past thoughts. It’s also an opportunity to do maintenance, like fix formatting based on new rules in my personal style guide.

# – micropost 22976

Local Government Association Cyber Incident Grab Bag for Local Authorities – Public Digital.

Along with other public services and businesses, cyber threats pose a significant risk for local authorities. The LGA wanted to provide practical support that could assist councils needing to respond to a serious cyber incident. They also wanted to make sure that the product clearly articulates how cyber security is a team sport, emphasising how a strong response hinges on collective strength.

 

# – micropost 22980

Is it just me or are other people still putting ‘please’ in their AI prompts?

# – micropost 22983

Thursday, 24 July, 2025

On user groups for local government software

Have had a few conversations lately with local gov folk which bemoaned the lack of active user groups for most software systems. This is a problem! What could we do about it?

It seems like vendors are keen to say they have user groups, but then once the sale is made, less keen on convening them.

There’s real advantages in the people actually using software to get together to share insight, issues, collectivise around requests, and so on.

Is there a space, I wonder, for an independent user group as a service offering? Someone to provide a safe place for online discussions, organise regular meet-ups, do a bit of the admin, and maybe engage with the vendors to get them to turn up and so on. Question is probably ‘who pays?’.

Another little LinkedIn post / rant, which I am saving for posterity here.

Tuesday, 15 July, 2025

Monday, 14 July, 2025

📅 Daily Note: July 14, 2025

Experiences of moving websites to LocalGov Drupal from the Essex Digital Service.

# – micropost 22965

Ben Holliday: New ways of organising:

What’s most interesting to me in 2025 is that we still need new ways of organising. It’s hard to point to places that we can truly call service organisations, at least outside of individual policy areas or transformation programmes.

# – micropost 22966

Jukesie – The Open Continuum:

Working in the open can seem scary and a bit all or nothing. I suspect I do not help with this with my stories of the extreme ups and downs of the practice and certainly there is some risk…not as much as is often feared but it is there.

Being open is not one size fits all though. There are levels to it and significant benefits at each of them – plus you build your muscles, instincts and a thicker skin if you work your way up to going all-out.

# – micropost 22967

Friday, 11 July, 2025

On ‘the single view of the customer’

“We need a single view of the customer!” Well, no you don’t, and you can’t have one anyway.

‘Single view of the customer’ is one of those easy to trot out phrases that sounds brilliantly simple and impossible to argue with when uttered with confidence. But just the slightest digging under the surface reveals a plethora of issues, whether technology, governance, ethics, data quality, affordability… the list goes on.

If anyone offers to sell you a single view of the customer for anything less than many millions of pounds, and needing at least 5 years to get working, then they are fibbing.

Instead, try bringing together the data you need about a certain type of customer, for a particular use case. All the debtors, for example. Then see if you or your software can spot trends or commonalities in that. You don’t need ALL the customer data to be able to make a difference, and trying to do so will slow you down so much that you’ll end up making no impact at all.

Another little LinkedIn post / rant, which I am saving for posterity here.

📅 Daily Note: July 11, 2025

Digital and mission-driven government: digital, burdens and networks – Richard Pope’s first essay of three looking at how his Platformland thinking “can provide a unifying role in the successful delivery of the government’s missions”.

In the digital age the answer is more subtle: using technology and digital-age design to systematically eliminate ‘administrative burdens’, one by one.

# – micropost 22941

How is it that I keep seeing these posts where people have made all these cool things with image generation AI, and I only ever get absolutely terrible results?!

# – micropost 22953

Is it worth bothering with LinkedIn articles any more? Seems easier and more engaging to just whack even longer form content into posts, as long as it fits into the character limit (3,000 or 500 words or so).

# – micropost 22954

James Plunkett: How to save bureaucracy from itself

I’m struck by how common it is these days to hear people working in government say some version of ‘bureaucracy is broken’, ranging from senior civil servants to political appointees.

These are thoughtful people, so their point isn’t that everything in government is broken. They’re just saying that the problem runs deep — that it’s not enough to try harder, or to run things better, because at least part of the problem relates to the logic by which bureaucracy functions.

If that’s right, what do we do about it? A principle I find helpful is the idea from systems theory that when a system fails we need to work at the level of the problem.

# – micropost 22957

Tom Loosemore: behind the scenes of the Universal Credit Reset – really interesting podcast episode.

# – micropost 22960

Thursday, 19 June, 2025

Content Restrictor WordPress plugin

For a project, I needed a way to easily restrict access to content on a WordPress website on a per user basis.

There’s loads of existing plugins that over complicate this significantly, so I thought I would test Gemini‘s capability at writing WordPress code.

The result is Content Restrictor – and it works very nicely for my needs:

  • Pages and posts have a check box – should this be restricted or not?
  • Each user page now has a section with a list of all the restricted pages, and if checked, that user can view the content, else they get a message
  • The message can be customised in the settings
  • There’s also a short code to display all the restricted pages that the current user has access to
  • Admins accounts bypass the restrictions entirely

If it works for you tool, feel free to grab it from GitHub!

Friday, 13 June, 2025

📄 Balancing ambition and caution in LGR

Chatting with Clare this morning about all things digital and local government reorganisation, I came to the conclusion that it really is all a balancing act. The risks of things going wrong are huge, and the importance of being ‘safe and legal’ is vital… but at the same time this is a generational opportunity for positive change and genuine transformation that must not be wasted.

So I think the answer for leaders going into this is: be ambitious, but be aware of the minefield you are working in. Be realistic about what can be achieved in what timescale, but absolutely make sure that at the right points in your roadmap (which ought to span a decade, if we are being honest) radical reform is on the agenda.

A couple of ideas on what that looks like. One of those inflection points is right at the beginning, when the business case is being put together and the design of the new organisation is being thought about. This is a moment for radicalism, for the new council to be infused with digital-age principles: responsive, user-centred, flexible, a positive actor within a wider system, preventative, relational, etc.

Do not, whatever you do, factor in any short term savings around digital and IT – it ain’t happening.

But when planning for day 1, I’d be cautious. Get everyone on the same Microsoft tenancy so you can at least all talk to each other. Having a single finance system will make managing budgets a hell of a lot easier. Make sure the basics of security are in the right place. A single website front end would be nice. I think that’s enough to be getting on with. Extend all the contracts that all the original councils had with existing suppliers – they aren’t going anywhere anytime soon.

Beyond day 1, we can start being radical again. Set out a realistic roadmap for the next 5 years or so, identifying the major service areas for redesign. This cannot, must not, just involve aggregating everyone onto a single system, but is the opportunity for ground up, blank sheet of paper style transformation, with the right technology a key part of making it happen. Don’t take on too much – even with a big team, these could take multiple years to complete.

From that point, iteratively keep circling around, don’t take on too much, manage expectations that real transformation is hard work, takes time, but is worth it. Each service area will be reached, at the right point in time, and until then, services must do the best they can with what they have – it’s worked oki-ish for the last 20 years, it can keep going another 5. Best not to rush, take the time and do it properly.

As I said at the beginning, keep in mind: we have to be ambitious, but those landmines are everywhere. Think about where you are treading, don’t be hasty. This is an amazing opportunity, so let’s not cock it up.

This was originally posted on LinkedIn, saved here for posterity.