In this series of blogposts I’m unpacking my opinions about the local government digital service debate. In the first post I set out my opinion that a single entity with the mandate and resource to address the common needs of the public is overdue and in the second I wondered about what that might mean for democracy. In this post I think about where services come from and in the others I wonder about how it might work in practice and finish off the series by considering the relevance of the GDS design principles in the context of local government. I hope it goes without saying that I don’t claim to have all the answers and want to know where my assumptions are completely barmy!
In the debate about meeting localised user needs in a coherent fashion it can be forgotten that it’s something that actually happens every day. There is a precedent for local residents to administer very postcode specific activities through a single product that is managed and delivered centrally.
They are not perfect examples of services that would be given the Digital by Default Service Standard seal of approval but that’s even better – they give the local government digital service lessons to learn and opportunities to iterate.
A first example would be the Blue Badge service. It is a piece of policy owned by the Department for Transport but which is administered by local councils. The digital service gives a consistent experience to the person who wants to apply for, change or renew their blue badge. That is a veneer on top of a complicated process but the complexity is hidden from the public allowing the service to be administered according to the local characteristics of the relevant council. The service is showing its age and has certain usability issues but here is a common user need served by a common digital service to administer a central government policy in a very localised way.