Daily note for 17 December 2023

Lovely bit of LocalGov blogging: Nature’s Genius: Service Innovation through Biomimicry.

This is a great story, about the wonder that was Yahoo Pipes, beautifully told… and now I am really interested in Retool, so I guess it did its job (tech marketers, take note)!

Working as a community to iterate the task list pattern:

We kicked off with an open call to join an online workshop, and had over 120 participants attend from dozens of government organisations. This helped us to understand the diversity of ways in which the task list pattern was being used, from application forms to case management systems, as well as collecting research findings, and user needs that the pattern was helping with.

From the workshops a smaller group, comprising designers and researchers from across different government departments, was formed to work on iterating the actual design.

Collaborating in this way wasn’t always fast – the work had to be fitted in around everyone’s main roles – but a dedicated Slack channel and semi-regular calls helped to maintain momentum.

Also this:

Daily note for 14 December 2023

Not been looking forward to today really. I have to go to see a foot specialist about an ulcerated wound on the balls of my right foot. It’ll be good to start getting it sorted, but it involves going somewhere I have never been before, not sure about parking etc, and the whole thing fills me a bit with worry.

I had no idea that Sarah Lay was back working in local gov, but am delighted she is.

A reflective, open and personal post from Carl. People – including ourselves – are not perfect, and that’s just the way it should be.

The challenge now for design in policy – I like a lot of the stuff in this post, which includes lessons that work for many relatively new disciplines, not just design.

WordPress and email

I’ve been moving a few of the sites that I manage away from a simple shared hosting arrangement onto something a bit more proper, with Steph’s advice (this blog, being incredibly simple albeit with a fairly hefty archive going back to 2004 or something, remains on the shared hosting for now). The new ‘platform’ is made up of using SpinupWP to manage the setup of the servers and WordPress itself, which is all hosted on DigitalOcean, with all the benefits that come from having this kind of control over the environment.

One area that has been causing me some worry is around sending emails out of these sites. The emails that WordPress sends, like password resets etc, can be a bit flakey in getting delivered at the best of times, but to make it more complicated, SpinupWP doesn’t install a means of sending emails itself, you have to configure your own, using an email sending provider like Amazon SES or Mailgun. It sounds complicated – and it is, in a way – but there are plugins and things to make it easier.

I’ve played with a few ways of doing it, but think I have settled on one, that I will now move all the sites onto over time. I’m going to be using the WP Mail SMTP plugin to get everything set up and working, and linking it up with SendLayer to do the actual emailing. When setting these things up, you need a domain to use, and each one needs configuring in SendLayer. To make life easier for myself, I have registered a specific domain to use for this, and so emails will come from sitename@davesemaildomain.notreal, which hopefully will keep things simple.

Daily note for 13 December 2023

Lloyd mentions how he likes writing the date at the top of his daily posts, as it reminds him of school. It does me too, on these posts, but also on the daily notes that I write more religiously using my Kindle Scribe. I am writing a log of pretty much everything that is happening, or that I see, or think, that feels particularly meaningful. It’s a marvellous aid to my memory, particularly as I discover more about how I struggle retaining information a lot of the time.

Indieblocks could be an easy-ish way of doing my preferred way of blogging through chunks and links in WordPress, maybe.

Am rather liking the challenging nature of some of dxw’s blogging these days: Service delivery is broken – it’s time to join it up.

Why Neil Williams writes weeknotes.

CAPE is quite interesting, collecting data and plans from councils on climate stuff.

Jeremy weeknoted. It really is just like old times.

GOV.UK Cookie banner and why it “won’t go away”

The struggles of the web browser.

Drafting the ‘so what?’ of the digital quality model

A bit of feedback from the recent call about the Local Government Digital Quality Model call was that the materials really need to sell the ‘so what’ around all of this.

I think there are 2 things here:

  • so what about the model
  • so what about being good at digital, design, data and technology

I have had a go at the second one initially, because I think this might make it easier to do the first one!

So, what I have come up with is this, as a first draft:

Why should councils care about the quality of their digital design, data and technology?

  • Efficiency – the better you are at digital, the cheaper and quicker your services will be at successfully meeting the needs of residents (etc)
  • Prevention – good use of digital helps the council to prevent need from arising in the first place, reducing demand on the council’s services
  • Resident (etc) experience – better use of digital means the users of services get a better experience, and are less likely to complain, or resort to other channels
  • Agility – councils with high quality approaches to digital are adaptive organisations, able to respond to change quickly and successfully
  • Risk reduction – good digital councils lessen the level of information security risk and the risk of projects or services not working as planned

As always I am struggling with the word resident – ‘user’ sounds too techie, and ‘customer’ puts a lot of people off. Any ideas for that?

Any feedback welcome!