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, not just initial functionality, of services they develop.
-
•
Embedding agile practices within public sector teams helps break linear, siloed development habits common in government.
-
•
Planning officers can evolve from domain experts to empowered collaborators and product owners within digital service teams.
-
•
Close interdisciplinary collaboration between designers and developers leads to shorter iteration cycles and better solutions.
-
•
Design principles focused on moving from documents to data and reducing noise guided development effectively.
-
•
Creating a platform that allows planners to assemble new application types themselves enabled rapid service expansion.
-
•
Service design scope needs to expand beyond users to include procurement, funding, policy, and ecosystem-level viability.
-
•
Building communities and coalitions across councils and government bodies is key to sustained adoption and service evolution.
-
•
Long-term impact includes up to 30% reduction in application processing time and fewer human errors.
-
•
Service designers must be flexible with roles and tools, focusing on learning and human-centered approaches to meet complex challenges.
Notable Quotes
"Should service designers have a role in the long-term viability of the services they develop? Our answer is yes."
"A viable service is one that not only functions well but can also develop, grow, and flourish."
"Rather than handing off work, our designers and developers work side by side through sketching, testing, and iteration."
"Planning officers became product owners, gaining confidence in agile and design processes through ongoing involvement."
"We shifted from building each application type individually to creating a platform that planners can use to build their own."
"Service design isn’t about the tools but the way of thinking to approach any problem with a humanist approach."
"Procurement in local government favors old, single-sale products, making adoption of new services challenging despite long-term savings."
"Our role shifted toward building communities that tackle common challenges and build a robust ecosystem."
"The coalition of the willing has organically developed into a community for change."
"Change is fundamentally about people—our approach lives out agile principles in service design to create a team that can build."
Or choose a question:
More Videos
"I want people to question why I’m not in the room if I’m not there."
Renee ReidBecoming a ResearchH.E.R (Highly Enterprise Ready)
June 3, 2019
"The pyramid has gotten so much larger; the number of people feeling special at the bottom is growing."
Chris Geison Dr. Jamika D. Burge Jemma AhmedWhat's Next for Research?
June 17, 2021
"Support software used to be really shitty and expensive, and Zendesk set out to fix that by making it beautifully simple."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"Processing limits and licensing terms currently restrict how much video and audio these AI tools can handle."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"B2B is b*******, it’s really just people that make up businesses."
Kit Unger Lada GorlenkoTheme 3 Intro
June 10, 2022
"I hammer on information architecture probably more than almost any other interviewer because I believe it’s the central part of the system."
Bob BaxleyLeading with Design Operations Past and Present
December 19, 2019
"A lot of things we said yes to didn’t necessarily have value to the member or the company — we had to challenge that."
Carla Casariego Sarah SpencerDesignOps in Wonderland
October 24, 2019
"Discovery doesn’t usually come with a launch party or even its own Jira ticket, but it’s what turns speed into progress."
Bianca JeffersonFrom Sprints to Systems: Operationalizing Continuous Discovery Through DesignOps
September 10, 2025
"Key is a reminder that these metrics reflect what is authoritative and important to the customer and the business."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
Latest Books All books
Dig deeper with the Rosenbot
In an AI and code-driven future, how does service design remain relevant for human-centered experiences?
How can cross-functional collaboration cultures be fostered to improve service design?
How do competing AI agents within an enterprise environment require new design approaches for prioritization and control?