Month: September 2017

Five for Friday (29/9/17)

blogphoto

Five for Friday took a little break for a month or so while I settled into my new job(s). If I’m honest, I am still not completely settled – it takes time getting used to a little portfolio having concentrated on a single role for several years – but I am getting there.

Enjoy the links.

  • Mapping service design and policy design – terrific post by Andrea Siodmok on how service design and policy design meet. Quite a lot of the focus on digital transformation misses out the policy element, and understanding what an organisation’s approach to an issue, and why it has that approach, is vital to defining services that deliver the intended outcome.
  • Digital transformation, or digital fossilisation? – good stuff from Andrew Larner talking about the need to use the opportunity of digital transformation to address big strategic issues around the manner in which organisations operate – not just hard baking inefficient and user unfriendly processes using new technology.
  • Defining Aggregators – you are probably bored of me banging on about Ben Thompson and how good he is, but this is another great piece, pulling together his recent thinking on digital operating models, diving deep into the concept of the aggregator. Now, the aggregator model might not be a good fit for public services, but it’s a great way to get thinking about this operating model malarky.
  • Designing for democracy – Catherine Howe applies the ladder of participation model to designing services in the digital age. Making this activity democratic involves the political, of courses, and also links up with Andrea’s post linked to above, where understanding the political and policy context is vital to achieving desired outcomes. There’s loads and loads in here (like does an iterative approach mean the big picture can get missed?) and it needs a good read and mull.
  • YC’s Essential Startup Advice – always take stuff like this with a pinch of salt (one shouldn’t ignore the pervasive Silicon Valley ideology that startups will save the world) but there’s some really good advice in here about launching new services. Much of it focuses on keeping things small and not worrying about scale until you know you have a thing that enough people like to require scale.

As always, these have mostly all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.

You can also sign up to get them delivered to you by email, if that’s your thing.

A digital journey

A tweet from Simon Wardley made me chuckle this week:

It stung a bit too – after all, I started out being someone promoting social media in government, and now here I am banging on about IT and transformation.

Of course, a bit of imposter syndrome is probably a good thing now and then – it never pays to be too confident, after all.

However, there is a bit of logic to my transition from hapless social media consultant to hapless digital transformation consultant, I think.

What I preached about social media was about getting on with things, making it easier and more convenient for residents and service users to access information, or make their views known. It was in a bit of a niche, around communications and engagement, but still.

However, as time went on, it became clear that this could only take you so far – you have to turn engagement into something actionable for a difference to be made. At this point I found myself in discussions with web teams and others around making websites more useful in delivering services (it was around this time that GDS started work on the single domain project).

Again, though, time passed and things didn’t move as quickly as I and others might have hoped. This was because, it turns out, that delivering great services online doesn’t just rely on a great website. It needs (at least) two other things: decent technology on the back end, and services fully designed to meet user need.

So it was at this point that, despite having started out in the social media days trying to work around IT, I realised it was necessary to fix IT in order to get even the simple things done properly. So here I am – modernising IT teams and helping organisations transform digitally.

Could I have started out at this point, ten years ago? Probably not. I needed to be hapless at social media so I could be hapless at websites so I could be hapless at IT and transformation.

Now I just need to work on being less hapless.

Language as an impediment to progress

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:

  1. 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)
  2. 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)
  3. 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.