Dave

On what we should call the folk who engage with local public services

Bit of an old chestnut, this, that I referred to in another post and I have been mulling on for a while.

User feels a bit techie, a bit too transactional, and sometimes like somebody who indulges in illicit substances. However it is delightfully generic.

Customers tend to have somewhere else to go, unlike many of those who engage with local public services. It does have it’s benefits though – it works for businesses and communities as well as individuals, and it is helpful to get colleagues to take improving the ‘customer’ experience seriously.

Citizens is a very complicated term in the UK, and besides, many of the people we work with are citizens of other places, not the UK.

Residents is one that I have liked for a while, but it doesn’t cover people who commute in, or visit for other reasons.

Businesses and community groups need to be factored in and the more individual terms don’t really cover this base. In work in the past, I have used the long and rather awkward ‘residents, communities, and businesses’. I now look on this period with a sense of shame.

On LinkedIn, Craig Hervey from Solihull asked why we don’t just use ‘the public’ – and he had a point. On mulling this though, I find the need for the definitive article a bit clumsy sometimes, and often plain old ‘public’ sounds just a bit weird.

On a current project working on digital strategy for a small local authority, I’ve needed to come up with a term to use, and this time I am trying to stick with ‘people’. Sometimes it can appear vague, which is a problem, but I then do a bit of work on the rest of the sentence to try and provide any additional context that is needed.

So that’s that, for now, for me. Those who engage with local public services are people.

Daily note for 18 December 2023

I’m barely posting any links into Raindrop. I just like linking to them here, on my blog. But I worry they get lost. Not that I ever seem to look for them.

I newslettered.

Some nice bits in Matt Mullenweg’s bag.

Public Digital’s data strategy playbook. Plenty of good stuff to learn from in here.

A literal twist on the classic Minesweeper game.

How product teams are using prototyping in the public sector:

A few teams were very mature in their prototyping practices. When they needed to move fast, try out loads of ideas and surface issues quickly, they used low-fidelity prototypes in paper, Powerpoint, and Mural or Miro. These helped them test out different journeys and flows. They progressed to Figma and Prototype Kit when they needed more fidelity or to test out technical approaches.

More good stuff from Steve: all of this post is worth reading, but the section on Cycles, not sprints is great:

For research and development work (like discovery and alpha), you need a little bit longer to get your head into a domain and have time to play around making scrappy prototypes. For build work, a two-week sprint isn’t really two weeks. With all the ceremonies required for co-ordination and sharing information – which is a lot more labour-intensive in remote-first settings – you lose a couple of days with two-week sprints.

Sprint goals suck too. It’s far too easy to push it along and limp from fortnight to fortnight, never really considering whether you should stop the workstream. It’s better to think about your appetite for doing something, and then to focus on getting valuable iterations out there rather than committing to a whole thing.

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.

Load more posts!