October 8, 2025, 3:33 pm

i’ve been enjoying Lloyd’s recent ponderings about blogging.

I’m also really enjoying the way this blog works these days, posting little nuggets that can get pulled into a aggregated post on a daily basis (or when I remember to hit the switch). Each of these ‘microposts’ exists as a separate item in the database, so you could see them all in one place, or even subscribe to the RSS feed for them. Massive thanks again to Steph for making this magic work for me.

I am aware that it’s very link-heavy, and I don’t write much here other than pointing to other people’s stuff. I’d like to write more and reading Lloyd’s stuff has been encouraging!

All this is possible because of open platforms like WordPress and standards like RSS. I don’t really understand what the ‘fediverse’ is, really, but it strikes me that there are two simple things that people need: somewhere to write, and somewhere to read.

I wonder if thing that blogging lacks is what we get with a lot of the walled gardens, which is the that the reading and the writing is in the same place. People like me are happy finding one service to subscribe to blogs in, and another to write posts in. But should WordPress (say) have an inbuilt aggregator? After all, we don’t read and write emails in different apps.

October 6, 2025, 1:10 pm

OpenReferralUK show and tell. I wrote on LinkedIn about it:

I genuinely believe there is a golden opportunity in the open referral stuff to use the service directory concept to flip the local public service operating model to matching people’s needs with those that can meet with – with local government getting out of the way.

October 6, 2025, 12:58 pm

Scott Colfer writes Most of What We Call a ‘Service’ Isn’t One (and Why That Matters for Product People)

In government and the wider public sector, we’ve built our identity around “services.”
Digital teams design them, measure them, apply the Service Standard to them.

But most of what we call a service isn’t actually a service.

More often, the work we label as a “service” is really something else:

  • An experience (like applying, enrolling, or updating).
  • A capability (like payments, case management, or publishing).
  • Or a technology system (like a website or platform).

The Service Standard itself, our flagship guidance, is rarely been applied to a true end-to-end service. Most of the time, it’s applied to fragments: experiences, capabilities, or tech.

And that mislabelling matters. You can end up treating a website like a whole service, or expecting a tech platform to deliver a citizen journey.