Resource. If you stop and think about it, it’s a terrible way to speak about people. A resource is something you take and use. Applied to people, it carries dismissive and devaluing undertones.
Stefan pointed to an interesting blog post this morning on Twitter, that states that the word ‘digital’ is becoming increasingly less useful over time:
I haven’t yet come up with a better word to replace “digital”. I’ve tried a few, but they have their own problems. There’s simply too much meaning packed in for it to be captured in a single word.
This is true of the word digital, but also many other words. Transformation is another good example. And let’s not get started on ‘customer’.
The working definition of ‘digital’ that I carry around in my head is digital = change + the internet. It works for me, in my context, but of course others don’t always see things the same way.
I’ve tried other ways of breaking it down with people to understand their expectations. One was a three way split:
- Digital access – taking a paper or telephone based process and whacking it online with an e-form (quick to do, few benefits except a bit of convenience for web savvy users)
- Digital efficiency – taking that process and digitising it end to end, involving the replacement or integration with back office systems, removing unnecessary admin touch points an so on (takes longer, more difficult, but yields better results)
- Digital transformation – taking an entire service and rethinking it from the ground up, knowing what we know about networks and connectivity (really hard, but could ensure the relevance of that service for the next 20 years).
This too is flawed, and by it’s nature most people would always opt for the middle one.
Of course, the current fad for digital transformation is just that – what we are talking about is technology enabled change, and the approach to doing that well really hasn’t changed much in a couple of decades. Understand your service in terms of where you add value and design an operating model to suit, re-engineer your processes to work well from a customer or user’s point of view, and then choose the best technology to run that process on.
The detail may change, and the tools and techniques might differ, but it’s basically the same thing, whatever we are calling it this week. Sometimes though you have to use the buzzwords to get people to listen to you – and perhaps that isn’t such a hardship, really.
I took a week off doing this last week – the shame! – so apologies for that*. A good crop this time round though. Enjoy!
- Tom Steinberg asks Why even bother with a user centred, digital government? and it’s a very interesting question. We spend a lot of time wondering what such a thing might look like, but without understanding why you’re doing it life can get very tricky. Tom’s answer is based around achieving compassion, fairness, the value of government itself, respect and transparency. Matt Jukes has posted his response to the question as well, in typically thoughtful style, adding empowerment to the list.
- An update on Government as a Platform (GaaP) progress at GDS gives a chance to discuss some of this stuff, including the opening up of the Notify service to local government, and the additonal capability for Notify to allow for inbound text messaging and the sending out of postal letters. Now, I wrote about GaaP a little while ago, and having just reread it, I’m not entirely happy about it (bit too tech-focused). The general issue I have with this area of work is that it seems to have leapt straight into the tech capabilities part, without thinking through the platform operating model bit first. The more specific issue with the way this is being done is in the re-writing of what are pretty common, commodity components. These things already exist! Why does local government need another way to send people emails, text messages or (FFS!) letters? Surely it would have been quicker, easier and cheaper to curate a suite of existing, well supported, easily configurable and interoperable components that could be used lego block style to build out services? Maybe there’s something here I’m just not getting.
- ‘Digital Transformation’ Is a Misnomer – is a great articulation about the problems of language and how they impede progress. I’ve a post in the process of percolation on this topic at the moment, however it’s worth saying that people’s understanding of terms is based as much on their own experience as it is commonly accepted definitions. In other words (ha!) no single expression is ever going to work as a shorthand that everybody gets first time. This whole thing is made harder by the efforts of vendor marketing departments who like to badge whatever they do with whatever the fashionable term is at the time. My approach is to choose the right language for your organisation and stick with it, and rather than focus on specific definitions, work on using them as symbols to represent the thing you’re trying to get across. Otherwise you are doomed to never get past the first slide of the deck you’re writing for that important meeting.
- If I could tell you 3 things – notes from a brief career in the public service – really nice reflective piece from Leisa Reichelt. All three of her things come from being user focused in one’s work, which is telling. It’s very easy to talk the talk on user needs but actually doing it is hard and requires constant vigiliance.
- GDS Isn’t Working – Part 5 (No Vision, No Ambition) – an excoriating post from Alan Mather, continuing his series analysing government transformation efforts of the last few years. It’s not perfect – I can’t help but get the feeling that Alan needs to let the Gateway go… – but it’s a great challenge to not just the current central government strategy but also for anybody working on this stuff in their own organisations.
As always, these have mostly all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.
* although nobody complained…