There are no digital silver bullets

In a fairly complex world, everyone yearns for a simple solution. The one thing they should do to make things better. The single solution to all their problems. Digital transformation is no different, and many of the marketers working in this space know it – that’s why they usually claim that their ‘platforms’ will deliver everything an organisation needs to change itself for the digital age.

Sometime people read a single solution into things when it isn’t there. A good example would be my post the other day talking about the uses of low code platforms. Several people got in touch questioning my assertion that it was the answer to all of local government’s problems. I replied pointing out that it wasn’t my assertion, and low code won’t fix everything. It might help for quite a few things though.

Overall, I am always very nervous of transformation programmes that have a single view of the operating model of an organisation, particularly when we are talking local government, which delivers such a bewildering array of services that it would surely be impossible to have just one way of changing and organising them all. Are there really that many similarities between running a theatre and processing benefits? Or picking up waste and community development?

Instead, part of laying the foundations of an approach to digital transformation should be developing an openness to trying new tools, techniques and technology, and an awareness of all the possibilities that are out there.

On the tools and techniques side, this means having a really good knowledge of ways of doing human centred design, innovation and delivery. Check out IDEO’s resources on this, along with the 100% Open toolkit, and of course the GDS service manual.

For technology, really consider the capabilities needed to deliver the outcome your users and your organisation want to achieve. See if you can match those to what you already have, but don’t shoe-horn them in. Think about the maturity of the capability you need: if it is really cutting edge, you may need to build it yourself (whether in-house or outsourced); for everything else there ought to be something on the market to suit. Whatever you do, don’t get bogged down trying to build silver bullets – a universal case management system for everything, or some kind of middleware utopia that makes everything talk to everything else. You’ll end up tying yourself into knots and running a huge IT programme, which is nobody’s idea of fun.

As I said, by all means re-use capabilities wherever you can. It might be that you do end up using one case management system for everything, because it works. Great! But find your way there by iteratively re-designing your way through services, matching capabilities to outcomes, and not through the implementation of a grand technology project.

So is there an operating model that can be applied to everything an organisation does? Probably not.

Is there a change process that can be applied to every service you deliver? Probably not.

Is there a technology platform that will enable you to replace every other system currently in use? Probably not.

Should you try things out, find some alignment between the outcome you want to achieve and the stuff you use to get there? Probably, yes.

Photo by Jens Lelie on Unsplash

LocalGovCamp 2014 thoughts #5 – tools

I found LocalGovCamp a really refreshing and cheering event this year. I’m going to spend a few quick posts writing up my thoughts.

There’s a kitbag of tools and approaches that can be used to tackle the problems facing us. Not everyone knows about them and this needs fixing.

I’m not necessarily talking about digital tools either – although there are some of those of course.

It’s more than that – it’s some of the emerging practices and processes, and mindset too. They don’t even cost money, most of these things.

Take the example from Carl Haggerty. At Devon they have a meeting room, decked out with fairly random, non-officey furniture, that can’t be booked out. It’s a room for the curious and the collaborative. You can have meetings in there, but be warned that anyone might turn up and join in. Or you could take your laptop in and get on with your day to day work, only sitting next to people who you don’t normally get to meet.

Like organisations acting responsively to their users. Being agile in the way services and products are delivered. Iterating in response to feedback. Co-designing to improve the way things work.

It’s also about a plurality of tools and systems to be used to help fix problems. I know this is a recurring theme of mine at the moment, but one size fits all solutions are dead.

People and organisations have to be flexible enough to be able to deliver different services in different ways to different groups depending on their needs.

This mindset, these tools and practices need to be rolled out to people in ways that will really help them bring about change. I don’t think training courses or online tooklits will cut it, somehow. We need something new.

Better blogging: separate writing and publishing?

I wonder if one way of helping the process of blogging is to separate the tools you use for writing and for publishing.

Here’s what I mean – when I use WordPress’ editor to compose a post from scratch, I am using the same software to write my content and to publish it.

I have nothing against the WordPress editor, by the way – it’s excellent. But I find that when I use it, I feel under a bit more pressure to get what I am writing finished, so I can hit that big publish button and be done with it.

Using a separate tool to compose the post, then transfer it to WordPress for publication makes the writing process a bit of a calmer affair.

I can still edit my content in the WordPress editor where I spot mistakes, or to add images, links and that sort of thing. The bulk of composition however, takes place in a different editor.

At the moment I mostly use Byword on the Mac and iOS for writing posts, which are then copied to WordPress.

What do you think? Am I talking nonsense – or do you also find that separating writing and publishing is helpful?

Link roundup

I find this stuff so you don’t have to:

Link roundup

I find this stuff so you don’t have to: