Uncategorized

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

Anti-patterns of behaviour in big organisations

Michael Coté has written an excellent post describing seven anti-patterns of behaviour in big organisations.

Number six is a particularly egregious crime, in my view:

Pay people to ignore them — BigCo’s love hiring new employees, paying them well, and then rarely listening to them. Instead, you hire outsiders and consultants who say similar things, but are listened to. In fact, the first task of any good management consultant team is to go interview all those bright, but ignored, employees you have and ask them what they’d do. The lesson is to track how many ideas come internally vs. externally and, rather than just blame your people for low internal idea generation, ask yourself if you’re just not listening.

Go read the whole lot – it’s good stuff.

The elements of council as a platform

A platform, yesterday

We are fairly aggressively targeting a platform approach to service design and delivery at Adur and Worthing.

Summing this up is the vision statement in our (still developing) strategy is: “To use our expertise and platforms to help the people, communities and businesses of Adur and Worthing achieve their goals.”

Government as a platform is a phrase that is bandied around a fair bit in digital circles and perhaps it’s worth thinking about what it means in the context of a local authority – hence the title of this post.

To me, there are three main elements:

1. Technology

Whilst it might not be the place we want to start, in many ways you can’t build a platform for a council without having the right technology in place first. Our approach has been to get the core tech foundations right, from which we can then figure out all the other stuff.

The essential thing to get about the technology stack is to think capabilities and not systems. Go watch the gubbins video if you haven’t already to get an introduction to this. In effect, pretty much every system is made up of similar core capabilities – think bookings, reporting, paying, case management, and so on. Rather than buying siloed systems which replicated a lot of these capabilities, the platform approach is to build each capability and then use these building blocks to put together systems to deliver services.

With this approach, you save money, have a common user interface across many systems, have interoperable systems that talk to each other, reduce support complexity and have a much more flexibility in your tech stack.

It also enables you to make use of best of breed technology, by making strategic decisions around buy or build. We don’t want to spend our time developing stuff in house that already exists on the market, where it meets our technology design principles (internet age, cloud ready, interoperable, plug and play…). However, where the market isn’t mature enough to meet our user needs, we have the ability to develop our own software that does. More on the detail on this soon – it really is exciting.

So far, so SOA. Platform technology doesn’t equal council as a platform. It is the foundation on which it is built, however.

2. Service (co)design

What really starts to make council as a platform a reality is the way that services are designed. In Tim O’Reilly’s classic talk on government as a platform, he compared the old way of delivering services to citizens as a vending machine – people pay their (tax) money in, and a service gets dispensed at them as a result.

A platform approach is less about the vending machine – where the first thing a citizen knows about a service is when it happens to them – and much more about involving service users in the design of those services in the first place.

This takes two forms. Much of the digital way of doing things has focused on the citizen or customer user journeys, and indeed this forms the starting point for all of our work. However we take just as seriously the needs of the internal user – in others words our colleagues who, up until now, have been subjected to some pretty awful software.

Our approach to digital transformation takes a truly end to end view, mapping existing processes, identifying steps that can be removed or speeded up, and developing the user stories that help inform a truly excellent user experience rather than a merely efficient one. Until this design work is done, the digital end of the transformation cannot begin.

By involving people, whether customers or staff, in the design of services, we switch the model from the vending machine to the platform. Services are no longer ‘done to’ people, or inflicted upon them, but instead built with them and their input at their very heart.

3. Let others build

We can’t call what we are doing council as a platform while the only people using the platform to deliver services is the council. What really pushes us towards a true platform approach is when other organisations are using our platform to deliver their own services and products,

This is where we really break out of this being a technology project, and into a far more interesting space where the role of the council in supporting local civic, community and business activity is redefined.

This could mean a number of things. It could mean the council effectively becoming a software developer for other organisations. Or, even more interestingly, it could mean other organisations building their systems on our platform using our building blocks of technology capability.

It would hopefully also include other organisations making use of other elements of our platform than just the technology. Our approach to service design, for example, as discussed above, could help organisations figure out the best way to deliver their products and services to meet the needs of their customers. This could be done by opening up our processes and making tools and expertise available to others to tap into.

Just the beginning…

We’re at the very start of this journey at the moment and none of the above is in place yet to the point where we can open it up to others. However, by planning for it at the start, it means the architecture of our technology and our processes will be able to deliver a platform to enable the Council to play a new, appropriate role within our local place in the future.

Making British Government easier to learn

My friend and colleague Jason Caplin pointed out today that the LSE have open up the lectures for their undergraduate course on British government and how it all works.

It’s a fantastic resource, and great that they have shared this openly, as it’s something that would be of use to anyone working in and around government.

However, the formatting isn’t all that great and it doesn’t work brilliantly on mobile. Plus, there’s no ability for learners to ask questions, leave comments or discuss the topics.

So, I very quickly threw together a WordPress site to rehouse the videos, using a nice simple responsive theme and layout. I also enabled comments, so there’s a bit of a social element there as well.

I’d be really interested to know from folk if this has been a worthwhile endeavour, and if you make use of the site. Also, if you have any suggestions for improvement.

The site is at http://britgov.learninglabs.org.uk/

Happy learning!

Load more posts!