Summary
As part of a MHCLG funded transformation programme, we were tasked with redesigning an outdated, manual planning system into one fit for the 21st century. Planning officers were grappling with systems that didn’t meet their needs. They were spending a lot of time on manual tasks and dealing with the impacts of human error. Our brief was to deliver a planning service designed by its users, in this case local authority planning officers. We took a radical approach of embedding with a team of subject matter experts, sharing knowledge around digital and agile as we went. This approach meant that user needs drove every action we took but also that the transformation of thinking and approaches from agile and service design started to have an impact on the local authorities themselves. We developed a set of design principles to keep both user needs and our collective vision at the heart of the process with a focus on moving from documents to data, reducing ‘noise’ and bringing the right information to users at the right time.
Key Insights
-
•
Service designers should take responsibility for the long-term viability, scalability, and adaptability of the services they help create.
-
•
Embedding agile principles into public sector service design enables more responsive, collaborative, and iterative development processes.
-
•
Developing blended teams of designers, developers, and domain experts working side-by-side shortens feedback loops and improves outcomes.
-
•
Planning officers evolved from limited domain experts to empowered product owners and champions of agile ways of working.
-
•
Creating platforms that enable local authorities to configure application types themselves fosters scalability and ownership.
-
•
Service designers must engage beyond traditional user needs to also address procurement, legislation, funding, and policy challenges.
-
•
Open and transparent collaboration across suppliers and stakeholders promotes consistent language and shared goals across complex ecosystems.
-
•
Moving from document-heavy to data-driven services reduces manual errors and processing times significantly.
-
•
Building communities and coalitions of users who collaborate accelerates adoption and drives continuous service improvement.
-
•
Service designers should embrace flexible roles and continuous learning rather than rigidly defining their remit.
Notable Quotes
"A viable service is one that not only functions well, but can also develop, grow, and flourish."
"We’ve been creating a team that can build and maintain a service, not just us as service designers, but all the people involved who will live with these systems after we are gone."
"Better software comes from individuals and interactions over processes and tools."
"Our devs are involved in sketching sessions and design feedback; they observe user testing alongside designers."
"We saw planners evolve from just domain experts to product owners capable of wider thinking about desirability, feasibility, and viability."
"We moved from designing each application type one at a time to creating a platform for planning experts to build new types themselves."
"The shift in the role of planning experts allowed planners to drive the process that enables change."
"User research and testing are vital, but it's the iteration of the service that uncovers nuances and unexpected behaviors."
"We didn’t have hard boundaries about what service design was or is; our roles shifted with the ecosystem’s development."
"Change is fundamentally about people, and agile principles help create teams that can build and adapt together."
Or choose a question:
More Videos
"You need well-defined frameworks and guardrails for experimentation success to prevent chaos across teams."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024
"You need sponsorship from senior leadership but also buy-in from all corners of the company to succeed."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"Sometimes clarity trumps consistency depending on the context or specific use case in the system."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"The canary in the coal mine is the bird that miners would bring in; if the canary isn’t doing well, there’s imminent danger and everyone needs to get out."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"It’s really hard to make changes to these systems because it’s risk-ridden and a major undertaking."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"The System Usability Scale is a powerful benchmarking tool, and reducing it to two questions makes it easier to collect."
Mackenzie Cockram Sara Branco Cunha Ian FranklinIntegrating Qualitative and Quantitative Research from Discovery to Live
December 16, 2022
"If you want to talk about the things you’re learning, use the hashtag DAS 2021 on Twitter, Instagram, or LinkedIn."
Bria AlexanderOpening Remarks
June 9, 2021
"Growth boards meetings are aimed around being very honest about the health of your product."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
"Soft eyes means zooming between the particular tree and the whole forest to see the bigger picture."
Dan HillDesigning for the infrastructures of everyday life
June 4, 2024