Be your own best customer to advance your transformation

One thing that has been taking up quite a bit of my attention lately is how, in the real world, an organisation can do the kind or big picture, strategic transformation that’s almost certainly needed whilst making progress on what might be termed everyday digitisation – the sort of thing that makes peoples lives easier but doesn’t dramatically change the core operating model of the organisation.

I’ve imperfectly defined three ways to attack digitisation before:

  • 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)
  • 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)
  • 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).

The problem is that transformation is where the real action is, but it is hard, so hard in fact that it’s difficult in my experience to get people to even talk about it. In the meantime, you’ve got folk shouting at you to increase self service or decrease unnecessary demand.

In a recent conversation with Catherine Howe I reminded myself about Ben Thompson’s great analysis of the Amazon purchase of the Whole Foods supermarket chain (Amazon is, I think, by far the most interesting company of our times). In it he describes the concept of Amazon being its own best customer. When building the AWS service for cloud based computing infrastructure, they had a huge customer ready and waiting to use it (and more importantly, test the hell out of it): the Amazon.com e-commerce site. Likewise, having its own in house supermarket would be a great way to build and test Amazon’s emerging logistics business.

This I think gives a hint towards the way an organisation (I’m thinking of my usual local government context, to be clear, although it could work in other sectors too) could start laying the foundations for genuine transformation whilst doing some of the quick wins stuff in efficiency, and maybe a bit of access if they really have to.

By having an idea of what the future big picture might look like, it’s possible to start building things in the here and now in such a way that it delivers the short term gain whilst creating the capabilities, the building blocks, for making the future happen too.

The danger is to drive yourself into a technical cul-de-sac delivering on the immediate requirements which leaves you hamstrung in your ability to execute on the much greater strategic win of genuine transformation when that opportunity arises.

As always the difficulty with this conversation is figuring out what that future looks like. It’s easy to write posts saying “digital isn’t about tech! It’s about changing your fundamental operating model!” but such posts rarely tell you what one of those operating models might be. I don’t necessarily have an answer to that myself (the consultant in me screams “it depends!” at this point) but I’ll post a few thoughts another time.

What I would say though is that the ‘be your own customer’ part of this does point to an organisation in the future being the provider, or perhaps steward, of technical capabilities that can be shared and re-used across a wider (perhaps local) system. However other assets could also play a part in this and it doesn’t need to be a technology focused discussion.

Photo credit: Jomjakkapat Parrueng on Unsplash

[RL] Accounts and portals

Original post from Salman Chaudhri, FutureGov

…a different, more nuanced approach to authentication can save councils money in the long run. By focusing on making the transactions that apply to most people as seamless as possible, it can help to reduce additional support i.e. the number of phone calls and face to face contact.

An interesting development on the original post by then FutureGover Carrie Bishop, who delightfully wrote “‘I really wish I had one place where I can see all my transactions with the council’, said nobody, ever.”

The idea of accounts for public services kind of makes sense in the abstract – people think of e-commerce and how logging into one place where all your stuff resides is a useful thing. Surely it would be great to have that for council services too?

As this post explains, that isn’t necessarily the case, not least because most people don’t interact with their council all that often, and when they do, creating an account seems like needless faff. In those cases, authenticating users in other ways makes much more sense, and there’s some great ideas shared here.

We’ve found that once you identify the information needed for different types of transactions it’s possible to strip back which services really need a ‘login’.

However when considering the user need, there are some cases where an account might make sense. Perhaps a business owner who has several interactions on a regular basis with different bits of the Council, like commercial waste and environmental health, for instance. Or a developer, who has several sites with planning applications ongoing, or building inspections.

It’s dangerous though to make assumptions about when an account might be needed, and this is certainly one of those areas where keeping that focus on meeting the needs of user can ensure a better experience for them, and creating a digital journey that’s more likely to succeed.


This is a post in the Reading List series, where I link to an interesting article and add some commentary. See here for more information, or find all the posts in the series here.

Two blockers to radical (digital) change

I was asked this morning for the two main blockers to progress in the various attempts at technology enabled change over the years, whether titled e-government or digital transformation.

Here’s what I came up with – it would be interesting to get your thoughts:

Two main challenges for me would be two elements of core capability. The first would be technology, and specifically software. The main line of business systems in use in most local councils is simply not fit for purpose for the digital age. They are horrible to use, don’t interoperate, work poorly on mobile, don’t offer great customer experience for self service and are dogs for the IT team to maintain. Time and time again, otherwise excellent initiatives at e-government or digital transformation are scuppered because of issues relating to core back office systems. What’s more, the market seems to find it impossible to have an impact on the situation, and so driving the incumbents out is very hard to do.

Second, and possibly more important, are the people issues. First is culture, which is risk and change averse, often because of the role of middle managers, many of whom are ‘experts’ in their service area and extremely dedicated to preserving the current way of doing things. Folk on the front line can often easily diagnose problems and suggest solutions, and senior executives are usually well up for a bit of disruptive change. However those in the middle can slow things down and block progress. The other bit of the people problem is capability, in that there aren’t enough really good people around in organisations to drive the change needed forward, which takes guts and stamina as well as intelligence. Without a reasonably sized army of these people in place, initiatives can get run into the ground very quickly.

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 democracyCatherine 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.