Rapid service design sprint with leaders
Leaders and managers on a rapid service design sprint helps them gain a new perspective that helps them to lead change
It can just take a week for a group of managers to have their deeply held view of their service to be transformed, and for them to create a new perspective and collaborative management style . The initial call was to help them look at their complex service, as they have critical problems that need addressing now.
The response to that is fine, I need a week of your and your senior managers time.
I did some prep first.
I would understand what the true scope for change is, according to what managers and practice leads will allow. What can we change, if anything. I met with the Director, the senior-most manager who would participate. And sounded them out. I understood their appetite for change, what they had done before, and what they expect.
For those who I had access to I also familiarised myself with the main problems that I would expect the team to come up with. So I have less surprises. I sounded some people in the group before-hand, to see what they might bring up.
I would also like to understand any dynamics in the group, and figure out how I might pacify those.
I detailed the five days, together with an internal consultant. We agreed the roles.
During the session I tended to do this:
- Quick check-in to place everyone at ease.
- Clarify with everyone the purpose of the session.
- I use a double diamond approach of diverge - converge for discussions.
- I might use a talking stick if needed.
This is what we did;
Day 1 A couple of hours of workshop, understanding the difference between different types of problems, and complexity. And how we as managers need to adapt to mange those differently. I used examples they would be familiar with. It was a discussion more than lecture.
In pairs, we went into the work, and sat next to the first group of front line staff (where the demand comes in). Learning what they do, what gets in their way, and the ability the front line staff have to do their real job. Sitting with staff is a way to help managers to see their operations from a perspective that is outside-in.
The rule is that we are there to learn, and we notified the local staff before-hand. We put the staff at ease, and said that we wanted to understand the problems they are facing.
Day 2 We review the learning from day 1. Learn a little more about what are the characteristics of good workflows by pooling our learning, and comparing this to the day 1 morning.. Then they go out to the main service delivery area and sit with the front line. This only takes an hour, but on their return to the room, they are buzzing. It takes almost two hours to unpack their learning!
Day 3 We go deeper into systems thinking concepts, and understand some key aspects of Service Design. We learn about the service user (customer) and what matters to them, and the journey. We also examine the aspects that lie behind the design of the workflows. And what management thinking are driving the behaviours of staff. We look at targets, etc.
Day 4 We listen to real feedback from a service user - and everyone is quiet. The managers realise that they have stopped listening to their service users a long time ago. The rest of the day is spent creating an end to end flow, and identifying points where they need to intervene.
Day 5 is summarising the improvement projects and systemic changes that are needed. Project sheet are created and owned, put on the walls, and off we go.
The response to that is fine, I need a week of your and your senior managers time.
I did some prep first.
I would understand what the true scope for change is, according to what managers and practice leads will allow. What can we change, if anything. I met with the Director, the senior-most manager who would participate. And sounded them out. I understood their appetite for change, what they had done before, and what they expect.
For those who I had access to I also familiarised myself with the main problems that I would expect the team to come up with. So I have less surprises. I sounded some people in the group before-hand, to see what they might bring up.
I would also like to understand any dynamics in the group, and figure out how I might pacify those.
I detailed the five days, together with an internal consultant. We agreed the roles.
During the session I tended to do this:
- Quick check-in to place everyone at ease.
- Clarify with everyone the purpose of the session.
- I use a double diamond approach of diverge - converge for discussions.
- I might use a talking stick if needed.
This is what we did;
Day 1 A couple of hours of workshop, understanding the difference between different types of problems, and complexity. And how we as managers need to adapt to mange those differently. I used examples they would be familiar with. It was a discussion more than lecture.
In pairs, we went into the work, and sat next to the first group of front line staff (where the demand comes in). Learning what they do, what gets in their way, and the ability the front line staff have to do their real job. Sitting with staff is a way to help managers to see their operations from a perspective that is outside-in.
The rule is that we are there to learn, and we notified the local staff before-hand. We put the staff at ease, and said that we wanted to understand the problems they are facing.
Day 2 We review the learning from day 1. Learn a little more about what are the characteristics of good workflows by pooling our learning, and comparing this to the day 1 morning.. Then they go out to the main service delivery area and sit with the front line. This only takes an hour, but on their return to the room, they are buzzing. It takes almost two hours to unpack their learning!
Day 3 We go deeper into systems thinking concepts, and understand some key aspects of Service Design. We learn about the service user (customer) and what matters to them, and the journey. We also examine the aspects that lie behind the design of the workflows. And what management thinking are driving the behaviours of staff. We look at targets, etc.
Day 4 We listen to real feedback from a service user - and everyone is quiet. The managers realise that they have stopped listening to their service users a long time ago. The rest of the day is spent creating an end to end flow, and identifying points where they need to intervene.
Day 5 is summarising the improvement projects and systemic changes that are needed. Project sheet are created and owned, put on the walls, and off we go.
The group of disparate managers have now formed into a single purpose driven team. They understand each other, and they see how in the past they have failed to even simply work together with one purpose. This is one of the problems of a traditional stakeholder analysis view. Not only is the outcome, practical steps towards improvement, the greatest change is in their mindset, systemic understanding, analysis of complexity, and new management behaviours that emerge by friday afternoon.
Helping them move from the left to the right
Focus on deparments and functions.
Top down communication. As a manager I already know. We dont have time for that. I am too busy to ask questions, I already know anyway. Focus on the short term performance. Push people harder. |
Focus on the overall end to end - the larger system.
Foster reflection and conversations. First, they get knowledge - they listen well. They enable networks of trust and collaboration to flourish. They learn, all the time, asking basic questions. Focus on long term value creation. Create well-being with staff. |