My learning working as a Service Designer on system changes in government
Working on systemic changes is hard by default. There are different areas of difficulty and problems that happen while working on them and it is hard even to get the basis of where to start, how to segment different parts of the system and understand different points of views that will affect the system. In this article I will be sharing the learnings I have gained working as a Service Designer on systemic changes in the Department for Education (DfE)’s Vacancy Authorisation, Recruitment, Joiners, Movers and Leavers system also known under the acronym RJML (the A for authorisation is silent in the acronym).
Before I jump into my newly learned understanding, a quick recap on what was the RJML project (just in case you haven’t already read my previous article… which I’m absolutely not judging you about… *glare in Slovene*). The RJML project was an 8 week long discovery project where I helped the Department for Education (DfE) map out their end-to-end system of Vacancy Authorisation, Recruitment, Joiners, Movers and Leavers stages. To do so, I have spoken to 10 different teams (process owners) involved in the system to get to understand their processes.
Having the understanding of the processes I have created a process map, found opportunity areas and presented them to the stakeholders. We have chosen one opportunity to start working on as a collective (all 10 teams together) and created ideas that they will start to prototype and implement into the system. I have worked on a work plan on how they will maintain the work after my 8 weeks with them and presented ways of working so that they can collaborate and work together.
These are my current bases that I have used to segment my work in while working on the RJML project:
1. Users
In the RJML project, we had different types of users. We had the end users (Candidates, Joiners, Movers and Leavers), and people supporting end users (Line managers, Vacancy holders) who were responsible for the creation of the vacancy, finding the right candidate for the vacancy, induction of the new joiner into DfE, and supporting people when they decide to either leave or move. Understanding users’ needs and where people are struggling is crucial to understanding what problem areas will have priority to be worked on and how they can be worked on.
2. People who work in the system / process owners
These people are usually people who will be working with you on the project, people who will be responsible for delivering the work as well as working in the system as their day to day job.
In the RJML project, these are people who understand the problems and are trying their best to solve them in the ways that they know. It was important to acknowledge their hard work and make them understand that we are here to help, not dismiss their work that they have done already. Showing them that they have the knowledge and understanding and I have the tools and methods that can help and support them in collaboratively solving the problems was a big part of my work. Working with 10 different teams and learning about their work knowledge really helped me understand that they all want to do what is best for people. It is just sometimes hard to see how they can do it and who those people are. Service designers can help support that understanding and show the teams how they can use their knowledge in new ways.
3. Business
This category is meant for directors, stakeholders as well as, policies, governance that constrain what is possible and how in the projects. Beyond that, support and understanding of the business are needed in order to have appropriate time to deliver systemic changes. Knowing what will work, what won’t, why and how are important questions that need the business view in order to be answered. Business needs to be involved and committed to the time and work that is needed to deliver. They are integral to showing commitment to supporting the work that needs to be done.
In the RJML project, the stakeholders were very interested in the project because there was interest shown to improve the internal processes at DfE by the permenant secretary. However, their understanding of system changes meant they saw delivering the improvements into the system as the main goal instead of seeing delivering improvements into the system as a way to achieve the goal. The actual end goal was to empower teams to be able to spot the opportunities and have embedded ways of working that will support the implementation of good changes, changes that are supported by user needs and tested out to see how they affect different parts of the system.
4. The system as it is now
Systems are alive and will constantly be changing, at least on micro levels. Therefore we need to understand that any system we map will not hold 100% accuracy to the current system. However, we can still use that as a base to learn how we can observe the system, indicate the opportunity areas as well as indicate what are the micro and macro changes and what effect do the changes we make bring into the system. Mapping out systems help us get an overview that is needed and helpful when we are trying to gain an understanding of who is responsible for the processes, who we need to involve in the co-creation of the ideas of improvement and who is going to be affected by our changes (testing the changes with them before they get implemented) and when the changes are implemented a system overview can help us track or showcase the changes more efficiently.
In RJML, system mapping helped teams understand how they are all connected. Although they are all responsible for their own processes, they are all also responsible for how users are likely to go through their process. Showcasing that to them was helping them understand that they need to work together to bring the needed changes into the system.
5. Ways of working
Systemic changes are never-ending processes that need to be embedded in the way teams owning the systems or services are working. Because of the living nature of systems, the only way we can make sure that we are making systemic changes that are intentional is if we make sure that teams owning the processes or services in the system have a collaborative approach and are willing to test things out. We need to teach and support teams around their ways of working so that they are enabled to spot the systemic problems, listen to users, work on problems together, and make sure that the proposed ideas for system changes are tested. Feedback is gained on how the changes will affect different parts of the system before the changes are implemented into the system.
In the RJML project, the teams struggle with ways of working more than understanding where the problems are. Therefore I have consciously introduced them and practised with the teams different ways of collaborative working that they can continue using to open up to each other, share and work on problems together. We started using Lucidspark (a collaborative digital whiteboard) that they could populate and use together. We have had a show and tell to share what we are up to and be transparent in sharing what we are doing. A big decision as to what problems will be tackled was made as a collective. Co-creation sessions with different team members from different teams brought different thinking to the ideas created in the session.
Comparing systems design to service design
Yes, the above elements are all the elements that we interact with as service designers. Looking at users’ needs, business perspective, constraints, and the current state of a service are all things that are part of service design, and I applied them to a system in a similar way I would with a service. It is all (or a lot) bigger, there are more points of view than you would normally have in a service. For example, in a service, there might be multiple process owners, but by the majority, the service is owned by one team or service owner. In the RJML system, there are 10+ process owners who need to learn how to work together and understand the whole end-to-end system they are responsible for. When testing ideas, people need to have as big of an overview as possible to capture any parts of the system that would be affected if intended changes are implemented because changes have intended and unintended effects on a bigger scale that need to be tracked.
I’m enjoying learning how I can stretch my service design tools and thinking into systems and am very grateful that I could do it on the RJML project. It is a starting point for many different projects and as anything, in systems, it won’t be easy. However, seeing DfE’s willingness to allow us to support and help them look at their systems, how they are working, who is being affected and how they can make changes is a big step towards where service design should be sitting and supporting organisations like DfE. And I hope I will be working on many similar projects shaping my understanding and moulding my ways of bringing systemic changes to our clients.
Follow Paper on LinkedIn