Skip to main content

Posts

A pattern and process library for local government

Patterns and processes are blueprints for digital services.

A pattern describes how a service interacts with the user to gather the information it needs to progress a  request. This will often be rendered visually on a screen, but increasingly it's also through voice, and devices such as smart speakers.

It informs the team designing the service of things like which questions should be asked, how many at a time, in which formats, in which order, and what the user needs to know to be able to complete the questions.

Processes are how the service is delivered, describing when and why a process interacts with the user, the service delivery team, third parties, digital elements such APIs, and anything else needed to deliver the service.

A graphic representation of a process for missed reporting bins designed using Business Process Model and Notation is below


but it can also be represented in a machine readable format too.

Patterns and processes are the most tangible part of a service an…
Recent posts

The Local Digital Declaration

Local e-government and digital isn't a new concept. In 2000, Implementing Electronic Government (IEG) aimed for all public services in England to be delivered electronically by 31 December 2005.

Local authorities reported 97% e-enablement at the start of 2006, but in reality what was created were websites crammed full of PDFs, and the legacy of this ethos still lives on with some councils. Mind you, an online form isn't always the best medium either, and recently we removed 60 online forms from our website.

Fast forward to 2013 and the Local Digital Alliance was formed which promised much but delivered nothing, and in 2016 the Local Digital Coalition saw many of the same organisations come together, to talk about, but not deliver a joined up approach to local government digital.

July 4th 2018 saw a Local Digital Declaration co-published by the Ministry for Housing, Communities and Local Government and many of the organisations in the Coalition. As you may have picked up from t…

Why we ditched 60 online forms

Whenever I read that a council is reaping the benefits of a digital transformation programme I go to their website and use one of their basic services. I go through the process to report a pothole, to apply for a new bin, or something similar right up until the point I would have to submit the request.

Generally the user experience is mixed and includes combinations of poor design, superfluous questions, jargon, wordy guidance text, and a requirement to create an account. Give it a go yourself and see how much user centred design played a part in their digital transformation.

At my place we have over a hundred online forms now. In some cases they send a simple email, in others they're the front end of a complex business process incorporating other services and applications. I'll be writing about the work we've done for waste services some time in the future.

Last week we finished removing 60 forms from our digital platform. Most had been online for four years, a few were a…

Low code isn't no code

There's been a lot of talk about "low code" over the past couple of months. At my place it's an approach that's starting to enable us to prototype and build new digital services a lot quicker than if we created everything in a framework such as .NET or Django.

We're near the start of our journey, and councils like Adur and Worthing are way ahead of us with this this approach, already creating line of business systems with a low code approach.

Whilst low code is often sold as an approach that means you don't have to write a single line of code, that isn't true. What is really means is that you write the code once, and you don't have to be a programmer to utilise it many times.

Take this example


This all you need to send a postcode the user has entered in an input box and return a list of addresses. Many services need a postcode lookup so we've utilised this quickly and easily tens of times.

Is it low code? Yes. Is it no code? No.

Below is the c…

A rough guide to central vs local government digital

More than ever there seems to be a willingness for civil servants and local government officers to work together to build digital services. Because of this I thought I'd put together a rough guide to councils and digital, for those working in central government digital.


There are lots of governments

First off, local government isn't a single government, it's hundreds, in fact over 420. There are blue, red, yellow (two kinds), green (but not that kind) and purple governments, some with no overall control (equivalent to a hung parliament) and one independent. More on this later.

To make matters more confusing, there are lots of networks, representative bodies and events too. I made a graph commons of all those I think relate to digital because I've tried to explain how I saw the relationships between them all so many times.

If you're looking for a single voice to talk to there isn't one because there is no Local Government, just local governments.


It's politica…

New plan, same idea.

At UKGovCamp in 2012, Sarah Lay and Carl Haggerty had an idea.

After a discussion with Sarah Jennings, a group of council officers were invited to London to talk about local government, digital and collaboration; I was lucky enough to be one of them.

We discussed the inadequacies of the annual Better Connected survey, what the new Government Digital Service might mean for local government, how we could work together to produce better websites, and a whole lot more.

Another meeting followed, and with the help of the Local Government Association, LocalGov Digital was created.

The idea grew and became LocalGovCamp 2014, and 2015, and 2016 and 2017. It became Unmentoring, the LocalGov Digital Slack Team, the Local Government Digital Service Standard, five local peer groups, and much more. We accomplished amazing things as a network with next to no funding, but we only got so far.

This is why in December 2017 we adopted a formal constitution which means LocalGov Digital is now an associati…

Let's not create a new legacy

Wouldn't it be great if all of government used open source technology? Imagine a catalogue of open source code, and organisations having the time and resource to use it.

Unfortunately, in the lower tiers of government that don't have large development and support teams, and which need to move quickly, it's not economically viable to do so. This is especially true where there are mature products and services that are easily consumable and available through markets like the G-Cloud.

Something arguably even more important than open source is open standards.

Whether you're using a standard for APIs like Open311, or writing code in open languages like JavaScript or open run-time environments like Node.js it means you can share integrations and developments. This week at my place we announced a Digital Collaboration Agreement with another council, and what's really going to help with this is the fact we're using common platform elements with open APIs, and building t…