Get posts sent to your inbox:
There was a time when MacOS was lauded for the quality of its design and user experience.

An online notebook
Get posts sent to your inbox:
An online notebook
There was a time when MacOS was lauded for the quality of its design and user experience.

Doug Belshaw – The (AI) Lottery Is Already Running:
AI tools arrived as things you could choose to try: chatbots, image generators, and the like. Pretty quickly, though, they’ve become things employers expect to be used, positioned as ‘things your competitors are already using’, and of course embedded in platforms on which we all depend.
That shift from you can use this to you can’t afford not to happened quickly and without anyone holding a vote.
Jerry Fishenden – A farewell to forms:
Citizens routinely suffer the consequences. Multiple services require us to complete near identical steps — finding and photocopying or scanning documents like passports and utility bills, filling out forms (online and offline) that ask for the same personal information, and waiting days or even weeks while an overstretched public employee cross-references and shares data across various systems before reaching a decision about our eligibility…
…But what if we could invert this model? What if we could implement a genuinely citizen-centred approach to service design, one built around the principle of instant proof of eligibility and not centralised and repetitive data collection and processing?
Ben Carpenter shares some recent updates to the service standard (LinkedIn warning):
We’ve made it extra clear in ‘Solve a whole problem for users’ and ‘Choose the right tools and technology’ that existing principles to design around users and not technology, and to reuse existing solutions, apply to AI technologies as they do to traditional digital technologies. This is the case throughout the Service Standard, but we have called it out specifically in those points.
There are also new requirements in ‘Have a multidisciplinary team’ for service teams using AI in a service to have someone on or available to the team who fully understands how it works and the impact of using it.
And ‘Choose the right tools and technology’ now requires teams to assess the impact of technologies on user experience, inclusion, and the reliability of information and decisions.
We have also specified that quality assurance testing must not be left to automated tools and that service teams must monitor outcomes for users and ethical issues such as bias.
Interesting writing project from Ben Welby – The Future of (Public Sector) Product Management in a Vibe Coded World:
Public service teams are at a kairos moment: a time when a new technical capability invites us to rethink almost everything about how we build and deliver services. But our centre of gravity isn’t swayed by “AI magic”. It rests on civic values we already know to be true: start from user needs; follow evidence over hunches; prize outcomes over outputs; prefer pragmatism to hype; fix the basics; and above all, put human worth and inclusion at the core. These are the ground we stand on when anything new arrives.
I’ve added auto-posting from this blog onto LinkedIn and Bluesky, using IFTTT to automate taking the RSS feed and turning it into posts on those networks.
I ran into an issue with the full posts being too long for Bluesky, so they didn’t get posted (LinkedIn has a more generous limitation I think).
Now, the simple thing would be to just tell WordPress via the settings to publish excerpts of posts via RSS rather than the full text – but I don’t want to! I like making it as easy as possible for folk to read this stuff. Or just send the post titles and a link to the socials – but I mostly don’t use post titles!
So, I called up Gemini and talked it through generating a small piece of code to generate an additional RSS feed just for social posting, that truncates at the 200 character mark (Bluesky’s limit is 300 but I am not sure if I need to leave space for links and things).
The feed seems to work, and this post will hopefully test to see if it works.
If anyone would like to see the code, just yell.
One of the projects I have been working on for the last 6 months or so is the playbook of support for councils going through reorganisation, which specifically looks at the digital and digital-adjacent things that need dealing with.
It’s really great to see it emerge in the open and for people to start using it to help them plan next steps as they approach reorganisation, which is an almost mind-bindingly complex operation, particularly when splitting counties as well as joining up districts.
We are also collecting people’s details via a signup form to build up our community of people feeding back and providing ideas for what’s next. The playbook has a long way to go to become even remotely comprehensive and more content launches will be happening over the next few months. By joining the community, you can have your say!
Take a look at the playbook and see what you think.
And don’t forget, the team will be represented at the upcoming LGR Camp, so that will be an opportunity to hear about the future of the playbook as well!
This is so good – Richard Pope has shared the detail as well as the slides for a talk on how his Platformland ideas should be applied to the NHS’ 10-year Plan. Loads to apply across the whole spectrum of public services in here.
But in years to come, we’ll look back and realise that the most significant impact of digital for the work of the public sector was not technology it was organisational. That’s because digital practice opens up a new way of working and running organisations. The model of iterative delivery may have first emerged as a way of building software, but it has since proven far more broadly applicable as a way of approaching complex problems.
Also, a brilliant way of properly sharing a talk. Thanks to Richard for taking the time out to do it.
Harry Metcalfe shares a cautionary tale of vibe coding and security:
But the arrival of these tools has – like all development tools that help get more done more easily – raised the security stakes. Tools like Lovable make building and deploying new websites trivial. In this case, one that collects personal data from real people: names, email addresses, postcodes, political opinions. They produce code that works, that looks professional, and that will pass a cursory glance from someone who isn’t a security specialist. But sometimes – often enough that it matters – they are built wide open and the tools don’t go to the trouble of checking, or telling you.