The challenge of service designers wading through the field of systems thinking, and how to prevent getting stuck at the first hurdle![]() Systems thinking with regard to organisations is conceptually very simple; it is a particular way of looking at the organisation, its environment, customers, and its place in the industry it is in, and everything that it is a part of it. When people start to see their organisation and role by seeing with a systems thinking mindset, they gain a perspective of it that is whole and interconnected, and this leads them to understand how that organisation can work in a fundamentally different way to traditional reductionist understanding. However, if you search for definitions of Systems Thinking it often creates more confusion than it solves. I would encourage those who wish to find out to search for definitions that they understand, (and a good place to start is the Ackoff video below) The more difficult part of this, is getting to that place of thinking systemically. Unfortunately there are no clear ways of doing that, and there are many weird and wonderful interpretations of how to get there. In this blog I will use Design Thinking as a comparison, because there are similarities with Systems Thinking (ST) due to the fact that they are both ways of seeing and understanding that are more fundamental to rational and mental analysis. Design Thinking and Systems ThinkingDesign Thinking was coined by someone awhile back (who and when is not important in this post). It became the subject of ‘papers’ and then become increasingly recognised. Then, someone else came along and made some significant and new strides in a direction of product development that they then linked to Design Thinking. What is so great about Design Thinking is the reluctance for those operating in that field to strictly define it, and more importantly to resist attempts to standardise and codify it. The day that happens will be the day it begins to die. So, we’re all doing some Design Thinking out there, and we all have slightly different approaches and ways. We are learning from each other, from those who dont do it very well, to those who seem to be naturally aligned. What Design Thinkers are not doing, is to create academic works that define it. Design thinking has always been around well before it was named. It is when we define it, name it, and then attempt to codify it does it then lose what it actually is. For those involved in this, you will know what I mean, and the excellent book Design Thinking Doing reflects this approach. Systems Thinking on the other hand, seems to have been defined early on by different small groups who were academically focused. While there is nothing wrong with that, much of Systems Thinking today seems to appeal to those who have focused on the academic aspect primarily. On the other hand there are many who use Systems Thinking in the workplace, disconnected from the theory, but they have no united voice or way to group together in the community way that Design Thinking has. Learning Systems Thinking? It’s not so Straightforward, lets ask Russ AckoffIt is very difficult for many people to truly get help in understanding the first rungs of the ladder of Systems Thinking unless you plunge into the theory. This seems to be a hangover of its history; starting in the realms of engineering, systems thinking appears to be rooted in theory through analytical analysis, rather than emergence and holistic understanding. So I want to separate Systems Thinking with systems theory. They are both quite different, and I many will first meet with systems theory when embarking on this journey of learning and discovery. Or you might stumble across open-ended global systems thinking discussions. A really interesting observation about those who focus on systems theory is the danger of believing that the theory is it. Theory is a rational and reductionist way of looking at anything, academia is not reality. Systems theory, when compared to Systems Thinking in action is different. They cannot really be compared because each are on diffrerent levels of reality. Each is not directly connected to each other, but they are directly linked. As an example of theory, when we use a model to describe something, we are not describing that thing directly. It is and always will be an artificial construct that we create to help us understand, and often it is a poor relation to the real thing. Theory might help someone analytically to become a Systems Thinker and for many this is the route for them, but it can also confuse and teach us about structured constructs and models only. Looking at Systems Thinking through a Systems Thinking lens, we would never reduce it to its component parts and then ‘teach’ those. For others it is far better to experience Systems Thinking, and learn from that. We need methodologies to help others in organisations to learn, but that methodology is not or ever will be Systems Thinking itself. The methodology or approach anyone takes is their way of undergoing a journey of Systems Thinking learning or application. What is Systems Thinking? I have chickened out and am going to rely on someone else to do this. This is a good place to hear someone talking about systems thinking, and how it fits into Design, Russ Ackoff And here is a definition that I like: Systems thinking is a 'mental model' of how we see and talk about our realities that help us to better understand and work with 'systems' that influence and shape the quality of our lives, Greth Evans Msc. Navigating the Systems thinking EnvironmentFocusing on the the correct definition of theory above all else can sometimes be characterised by people expressing particular behaviours, especially on social media. I have found that these not only hinder learning, but often do not help. This is what I sometimes witness:
Sometimes perfectly normal and rational people become seemingly posessed by some sort of primeval behaviours! The splintering of the systems movement into warring factions championing soft systems thinking against hard systems thinking and critical systems thinking against soft systems thinking may provide amusement to academics but is alienating to practitioners. MICHAEL C. JACKSON When applied to organisations, Systems Thinking should be reversing the impact of reductionist, Taylorism and rigid scientific thinking; it should be pointing us to novel ways of seeing and managing. It could be heralding new benefits that coincide with Design Thinking and its associated mindset and culture. Design Thinking and Systems Thinking go hand in hand. For me, part of the beauty and power of Systems Thinking is its inclusion of everything that incorporates the total aspects of organisations, including human beings and their behaviour. And as for my journey, I was lucky enough to meet some people who have spent much time analysing theories, but more importantly, to learn from the reality of current organisations and how we operate within them. Putting that theory into practice. For me, the understanding and application of Systems Thinking has developed through experience, a mindset of learning, and the application of ideas and concepts to discover their impact. Design Thinking could have gone down the same sorry path as Systems Thinking, but it luckily got led by those who were open, flexible and understood emergence of thinking through learning. Moving ForwardWhat do I suggest for others to move forward? I am not exactly sure, and I would welcome suggestions. I would encourage learners to seek out those who they resonate with, and reject those who they dont. Read, connect, visit, and work with those you find attracted to, and move away from those who you find express behaviours and attitudes that repulse. Thats what I did, and it has helped me. Oh, and the most important thing, practice it, do it, make mistakes and apply and learn. I have found that Systems Thinking that is published is often applied to world problems, or natural systems, or derived from the early days to Engineering. If we look at the models and concepts that are created to communicate that type of application of Systems Thinking, I find that they can be often unhelpful to learn from when looking at services and organisations. I dont recognise the similarity of an organisation being a natural ‘thing’ like a cell or a human body, nor is it a logical robot, and as such perhaps be courageous enough to create your own understanding of organisations when helping yourself to think more systemically. The way I understand how able someone is to see an organisation through a Systems Thinking lens is to have a conversation with them, and listen to how how they see and therefore speak about that organisation. Their concepts and how they express them will link to their thinking. Complexity & GrintComplexity, It messes with our Rationality. Let go of that rationality as a cage and allow complexity to become normal. Understanding complexity, and therefore releasing my prevailing and rational mindset, has helped me to understand why I failed to sustain much of what I was trying to do in the past, with managing operations and people, implementing change, creating and implementing IT systems. I, like so many others, have looked back and seen the frustration and struggle to ‘get things to stick’ and how I used to blame others for that failure. What I now realise, apart from a different style of management in general, is that the mechanisms (control, skills, behaviours, etc) that operate with complexity, are quite different to the mechanisms that are needed to dealing with complicated but rational services and problems. Understanding when to use which ones helps managers to understand why sometimes their efforts are successful or futile. In the public sector in particular, managers that I see assume that their learned understanding of management is rooted in those derived from complicated rational systems. There are many resources now available at the click of a button, so I wont go into details here, but I have found the simplicity of Grint a very helpful starting point. My experience of Outcomes of Good Service DesignAs an exercise, which I do not know if has any value out not, I have decided to write a first draft of a set of Good Service Design principles. (I was inspired by Rams the product designers principles). Any feedback would be welcome, as I expect these principles to change significantly:
The Foundations of what I do These are some of my Systems Thinking & Complexity principles listed, that I use as a foundation to what I do.
Regardless of the organisation and system characteristics; this is primarily about human beings working together to solve the problems of other human beings. Team working, behaviours, direct communication, respect, humanity, are all key aspects of this work. Digital Design follows from this Service Design, and the human and formal interactions that are created. It is easy to remember theory with the mind; the problem is to remember with the body. The goal is to know & do instinctively. Having the spirit to endure the training & practice is the first step on the road to understanding. Qualities Required to Becoming a Systems Thinker?
0 Comments
This quote by Tim Brown recently describes the shift in Design Thinking activity with organisations that is happening worldwide. The shift is from the initial concept of product design and fitting that into a stable organisation. Now, service designers are increasingly called to integrate their work within the business itself. In his quote Tim Brown specifically refers to the design of the underlying end to end service. For those seasoned practitioners who have been working in Service Design, this should come as no surprise, as it is becoming an increasing reality in our work.
Is this good? The impact this is having on service designers is less about theoretical discussions about being right or wrong, it is driven by the market demand. And it is being driven by the market because Service Design is maturing into he next stage in its development; it is moving from an innovative and dynamic start-up, to a more accepted mature methodology, slowly becoming integrated into businesses. That in itself is very interesting, as it is another indicator that proves the worth of Service Design through its acceptance by mainstream businesses. So, it perhaps has to be accepted as a positive milestone on the path to providing greater value. What approach and skills are needed to fulfil this shift? The question has been bounced around conferences and discussion in the last few years, and is being currently tested by those in the thick of the service design workplace. From recent observations with that work that is published and has demonstrates proven success, these are some of the points that are surfacing: 1. Familiarisation with business concepts and skills have to be present when undertaking service design in a business context. 2. Service Design and business transformation skills and methods have to go hand in hand at various points in application of Design Thinking, and the relationship with the client. 3. Design Thinking has specific unique principles and characteristics that are central to its definition, and traditional methods of transformation are mostly not aligned to these principles. Therefore additional transformation disciplines have to become realised through approaches and mindsets like Systems Thinking, Teal, and other modern concepts. This will allow Service Designers to leverage their new approaches into business services efficiently and effectively. In fact, efficiency and effectiveness need to become part of Service Design. How to do this. These three points do not mean that all service designers have to become proficient in them, but designers will be increasingly co-designing their services in collaboration with like-minded team members who have got that proficiency. They have to work with those who share their principles of working and culture. Service Design agencies are already sourcing those contacts into their work. The Role of Digital. Lastly and perhaps most striking, is that if Design Thinking has to include truly redesigning services, designers have to be able to wean themselves off the single minded focus on Digital as being the only means by which to achieve transformation. The transformation of services is far more about people, behaviours, purpose, and the workflow, than it is about any one specialisation. Why do I say that Digital might have to be not the only design specialism? Well, I deal with plenty of complexity with some services. This is particularly relevant in the public and health sectors, where as soon as we move away from the most simplistic services, we land right in there middle of complexity. And in service design, complexity is often not the best way to deal with that complexity. In England we have plenty of examples of that. If that is widespread, that will certainly push Design Thinking into wider contexts! A recent example I saw recently, in a London Borough Council, was a new customer system for helping people walking in. It was for Housing. It went like this;
In the week I was there someone was so shocked by the service they were getting and they were in such a mess, that they took an overdose whilst sitting talking to the housing officer. They were in hospital for two days. And no, they did not have severe mental health issues. That same week, in another housing department in the country, a person set themselves alight in the same situation. Whoever designed that Digital service has lots to learn about SD Having just got back from a public sector conference, looking over the day and asking myself the question as to whether or not these gatherings help? The answer is yes, many people discussed good things that teams are doing, and agreeing what we should be doing. But one phrase from the conference really did trouble me; We now know what we need to do to make Transformation work’ And then someone reminded me of something. They showed me a report with this great list of innovative health & social care working principles:
Now imagine the The Health Minister agreeing the above and stating in Parliament; The theme of the plan is to harness the efforts of the community in both the statutory and voluntary sense. That is very much in line with the Government's view. Well, this list and this quote is from the Secretary of State for Social Services in 1982! The realisation that dawned on me that we have been there before, and we’ve revisited this several times in the last decades, was a jolt. Does anyone reading this recognise that those wanting the job to transform health & social care, where after several decades, realise that their work has made no meaningful impact? They all seem to be doing good work, but with almost no real lasting difference. We try and make improvements, but what about those who work there? What can it be like for them? Imagine that when an NHS nurse gets to work starting their shift, that their manager slaps them in the face, then later on the manager sticks a pin in their leg, so it bleeds. Then at lunchtime, the manager hits the nurse over the head and causes a headache. What would we think of the behaviour of that manager? Obviously this account is ridiculous and would never be acceptable. But if so, then why do we accept this behaviour when the abuse does not lead to any obvious physical damage? We encourage nurses and social workers to train, and encourage them to accept low pay with the promise of having a job that really matters. And then, when they start the job, we ensure they can never do a job as they were trained to do, because there is not enough time. And we command them to stop using their brain and follow simple and stupefying instructions, so that they cannot really help the patient in the promised way. And we treat them to the point where they often cry with frustration on their drive home. How have we come to accept this abuse? This mindset that we have developed leads to ridiculous accepted conclusions; 1. What is one of the problems of the NHS? We don’t have enough nurses. The root cause of the symptom of not enough nurses is that the nurses we train, start work, get abused by the NHS system, and leave. We have always had plenty of nurses being trained, we simply throw the opportunity away, and damage careers in the meantime. Can it be morally right to convince, train and then give someone a job that is not possible to be morally fulfilled? Taking the same situation but with a plasterer who plasters the walls of old properties, the result of this situation for the plasterer would be a poorly and partially plastered wall. Would anyone simply accept that? Imagine thousands of new houses with partially plastered walls, is a ridiculous outcome to contemplate. But why do we accept this in our public services? Is it because plastering is physical that we can see it so obviously? Management of Public Services Managers in the public sector are not one homogeneous mass, but they do seem to behave in a similar way. Whether managing nurses, council officers or road repairs, their answer in a situation where a member of staff cannot complete the task given to them for that day is in many cases a shrug of the shoulders. The one time that a manager has to use their ability to lead and manage operations, they abstain in the worst possible way. Managers are paid more, and part of their role is to manage and maintain the operations and delivery of services funded by the public for the public. One hundred years ago the Suffragettes managed to get 50,000 people to march to London; before phones and the internet. They were showing the world that the situation had got to the point that it desperately needed to change. What should our leaders in the public services be doing to highlight an impossible and abusive situation? Certainly not simply shrugging their shoulders - why can't they sit on the steps of Whitehall for a day in demonstration. NHS leaders are somehow subservient to their hierarchical masters, but surely their job is also to push upwards to their bosses? Public sector leaders have a duty to highlight and ensure critical aspects of the organisation, not simply to act as top down mouthpieces. The Windrush issue is an example of managers having to follow and not react to bad culture. Lastly, what of the impact on the most important group of all - those the services are helping - Us, the public? This could be the subject of another article - but what of those millions of interactions since 1982, that could so easily have different outcomes. At times, managers can and do get dismissed from their job because they say something that is overheard, published and deemed racist or suchlike. But when managers ignore and take advantage of their staff, there is no public outcry - they carry on with their job. Are a few misplaced comments far more important than peoples livelihoods? The Cause of the Problem Enough wringing of hands, and bemoaning the lack of political will. Moving past despondency and looking for hope, lets look for the systemic cause of the problem. Why after 35 years can we not implement real transformation? For me, the answer emerges surprisingly quickly and clearly. Those who Govern the System Elected politicians, MPs, on election day are suddenly pushed behind a desk and have to run the public sector. They have to oversee a hugely complex and large organisation. Would they know if Universal Credit is a good idea? You can ask this question to people whose job it is to deliver benefits and half will say yes, and the other half say no. It is a complex issue that can only be answered by understanding the whole system, and how people truly interact with it - understanding it as a real behavioural set of individual workflows. Imagine MPs attempting to make clear judgements in the middle of the myriad of conflicting pressures that they face daily. Its not heir fault, its the situation they find themselves in - needing to make policy decisions before the next minister arrives. The Structure The direct imposition of short term political decision-making on the long term nature of public service is an ill-matched structure of control or governance. Politics is an emotional and illogical maelstrom of ideology and decision making, and these characteristics are the opposite of the characteristics required by the structural nature and purpose of the public sector services we expect politicians to be able to oversee. We watch as expectant policies are kept out of the meandering reach of decision-makers; lost opportunities for key decisions, indecision, and fear of election consequences - demonstrating clearly that those decisions that are needed are simply too large and complex for the political environment at that time. MPs or councillors do not control public services, but they do create the environment and governance by which those services operate. A good example of this is how the imposition of austerity has driven the public sector recently. Also, central government has an important task in defining elements of the wider system - like management competence, digitalisation, etc. So, if it is so difficult to know what to do in the face of a barrage of conflicting information, it is the height of irrationality to expect MPs and the collection of those who report to them, to effectively oversee such complexity. And no, the Civil Service cannot do it either - they are good at bureaucracy and administration and maintaining control, not managing complexity. If this was a large private sector multi-national, the CEO would put in plans to change the structure and replace leaders with ones that have the correct competence. It could be completed in six months. There is no practical reason why this cannot start to happen in the public sector, if the will was there. And it would free up politicians to do the job that they are good at doing - from a distance. It seems Incredibly Difficult to Achieve When I work with managers they are quick to explain the a number of reasons as to why a particular change cannot happen. It is the nature of the culture that we see that the public sector is full of barriers to moving forward. However, when working with certain senior managers it can be demonstrated, and to their great surprise, that these barriers can be overcome. When working with teams to develop new approaches, there always comes a time when making forward progress, the team realise that they have broken the public sector spell of continually struggling in decision quicksand. From that point forward, the team move into a new decision-making paradigm, and we move into new territory of true change. What is the Root Cause? We actually know how to run public services well, there are islands of examples using innovative methods that have demonstrated a transformation from the old style public sector administrative master-servant relationship. We have seen that services can be transformed so people in need can be guided to get their lives back on track, and communities can rediscover their strength. Many times these fledgeling examples are caught up in larger pressures, that then throttle their existence; they need to have the appropriate underlying long term alignment across the public sector to continue and thrive to other areas. Most of the truly transformative change I have been a part of has reverted back to 'normality' due in all cases to new managers taking over the service, and bringing their old management style and behaviour with them. What is a Solution?
There are people who know how to understand, and then manage operational complexity. And there are also clever people who can make things happen. Find those with both attributes, and put them in a room together, that also spans a cross-party political landscape - ideology has to take a back seat here. That group then leads that part of the public sector - they decide the structure, what methodologies are most valid based on evidence, manage transformation through proven prototypes, and ensure the appropriate leadership competence is promulgated throughout the sector. So that the transformation can emerge to all parts of the sector. Their strategic vision will span 25 years. They could plan for changes in technology and demand, tackling preventative longer term solutions to impact on problematic root causes. And their appointment to the group is neither as elected officials or private sector capitalists. They would be a unique group whose selection has to be decided with caution and transparency. An Example Using the example of the problem of ‘not enough nurses,’ that group could ensure that nurses are able to do their job by ensuring a minimum number of nurses in given situations, and that the nurses are treated with a level of management attention and approach that is now expected in any other industry. They would define management competence and ensure management suitability to those competencies. Most importantly, they would understand the core journeys service users take through the NHS, and they would ensure the structure and services are designed to match those user journeys. Political (public) oversight must still be in place, with the ability to ensure that the public leadership group is doing the right job. So is the systemic answer is that we need a different governance structure? Housing Allocations CBL and the impact of a systems thinking approach in such a complex world
|
UnderstandThe team worked for four weeks, to gain an understanding of how the system worked. We discovered that all the demands could be classified as
The team worked for four weeks, to gain an understanding of how the system worked. We discovered that all the demands could be classified as
|
|
These are a few examples of what we found in the first two weeks:
After 4 weeks of investigating, this is what we learned about the service we all had been working in:
The team now had hard evidence that how their current procedures worked did not produce a very effective or an efficient service. By this point the team were very enthusiastic to make changes – but were unsure exactly what to do.
The Work – Community Safety
To understand the process that the council staff take is not straightforward, because there is no typical problem. Imagine a community – anything that annoys anyone in that community is dealt with by this group. They called themselves Community Safety. But it is how the problem is viewed and resolved that is the key to a better service.
Example - A problem with Rubbish
This is a story of two people John and Sandra, who both have domestic rubbish accumulating in the garden.
John, has accumulated an amount of rubbish on his front garden. And this is the workflow:
Looking at John’s situation; he has recently split from his wife, and has let things in his life get out of hand. He has been away visiting relatives for a week, and just got back to work. When he got the letter from the officer, he recognised that he needed to tidy the garden up and did that.
Comparing John with Sandra
Sandra has accumulated an amount of rubbish on her front garden. And this is her workflow:
Looking at Sandra's situation. Sandra, has an uncle, who was released from prison, stay at her house for several weeks. The uncle sometimes invites strange guests into Sandra’s house. One of Sandra’s children is out of control, and she often screams at the child. Sandra is very unhappy, feels alone and unsupported.
Sandra often just cannot cope with the normal things in life that need to be done – it has all got too much. She does what she can to reduce any problems. To cope she tries to live with someone but she has lived with other men in the last three years, and they have sometimes abused her. Because of the extra people in the house, there is more rubbish than fits in the standard waste bin that Sandra has been given.
Every time Sandra gets a letter from the council it’s a new problem for her, to add to the already long list. How is she meant to get rid of the rubbish? She does not have a car. So to reduce her daily worry she simply throws all council letters, unopened, in the bin. When she got a letter from the council about her rubbish, she threw it in the bin.
The Learning
The current council approach is to treat every case of rubbish in a garden in the same standard way. But we are discovering that different people have got very different needs.
- The team began to realise that we kept getting repeat calls. The team complained that the public just did not seem to listen. But we had to be fair and give the same service to all.
- The public seemed to react quite badly when we said that we had the power to fine them, - but we have a procedure to follow.
- We automatically fined people for throwing some of their rubbish round the corner. We had to treat everyone the same. Some people got very annoyed at this, and this puzzled us.
After 4 weeks of investigating, this is what we learned about the service we all had been working in:
- There were many people we dealt with that we just did not help, we made their overall situation worse.
- We spent lots of time on things that added no value to anyone.
- 70% of demands were investigated, but never resolved.
- 75% of the demands changed from what their original demand was.
- 60% of people we deal with are recorded on 3 or more separate computer systems.
- In 85% of all cases examined, the team have discovered that the person is having additional issues with other council services – in other words the person is complex.
The team now had hard evidence that how their current procedures worked did not produce a very effective or an efficient service. By this point the team were very enthusiastic to make changes – but were unsure exactly what to do.
The Work – Community Safety
To understand the process that the council staff take is not straightforward, because there is no typical problem. Imagine a community – anything that annoys anyone in that community is dealt with by this group. They called themselves Community Safety. But it is how the problem is viewed and resolved that is the key to a better service.
Example - A problem with Rubbish
This is a story of two people John and Sandra, who both have domestic rubbish accumulating in the garden.
John, has accumulated an amount of rubbish on his front garden. And this is the workflow:
- Someone in the community complains.
- A call taker, follows a standard procedure, records the details on a system. This becomes a task.
- The task gets sent to the manager, who after a few days prioritises it and sends it to an officer.
- The nominated council officer visits the house, knocks on the door and tries to speak to the person inside. But John is at work.
- The officer returns to their office, creates an official letter at their computer, completes the IT system details of the failed visit, and posts the letter.
- John gets an official letter from the council that states that the rubbish contravenes his housing tenancy agreement. It also says that if the rubbish is not moved within a week, a fine will be applied.
- John quickly removes the rubbish, he drives it to the local tip. The subsequent visit by the council officer finds that the waste has been removed, and the council has rightly done their job.
Looking at John’s situation; he has recently split from his wife, and has let things in his life get out of hand. He has been away visiting relatives for a week, and just got back to work. When he got the letter from the officer, he recognised that he needed to tidy the garden up and did that.
Comparing John with Sandra
Sandra has accumulated an amount of rubbish on her front garden. And this is her workflow:
- She gets the same visit, and letter. But Sandra has not moved the rubbish within the week. The council officer visits again and verbally tells Sandra that he now has to fine her. Sandra swears at the officer and slams the door.
- The officer, then goes back to the office and writes up the whole scenario on the IT system. But the officer has been trained to be customer focused, so the officer makes several visits to talk to Sandra in the next weeks – delivering letters when the door is not answered.
- Sandra eventually throws the rubbish over the fence nearby, and the officer is not happy about this.
- Sandra is fined. But because she cannot afford the fine, the council agrees for her to pay small amounts every week.
- The council go and pick up the rubbish and take it to the tip.
Looking at Sandra's situation. Sandra, has an uncle, who was released from prison, stay at her house for several weeks. The uncle sometimes invites strange guests into Sandra’s house. One of Sandra’s children is out of control, and she often screams at the child. Sandra is very unhappy, feels alone and unsupported.
Sandra often just cannot cope with the normal things in life that need to be done – it has all got too much. She does what she can to reduce any problems. To cope she tries to live with someone but she has lived with other men in the last three years, and they have sometimes abused her. Because of the extra people in the house, there is more rubbish than fits in the standard waste bin that Sandra has been given.
Every time Sandra gets a letter from the council it’s a new problem for her, to add to the already long list. How is she meant to get rid of the rubbish? She does not have a car. So to reduce her daily worry she simply throws all council letters, unopened, in the bin. When she got a letter from the council about her rubbish, she threw it in the bin.
The Learning
The current council approach is to treat every case of rubbish in a garden in the same standard way. But we are discovering that different people have got very different needs.
Giving John the letter to tidy his garden helped him to keep his life under control.
|
compared to
|
Giving Sandra the same letter as John, made her life worse. It pushed her level of need just one more step higher than it was. And it may have cleared up some of her garden, but all she did was remove the problem from her sight.
|
​The Prototype and the New Approach
The team spent several weeks learning, taking the next cases that came into the council at random, and tried to perform them in a better way. And for each case, they compared both approaches by measuring what happened, and estimating what would have happened in the old way of working.
These are team insights that were then taken forward to design the new approach:
The team analysed the root causes of the issues they dealt with, and they were: low level anxiety, depression, childhood issues, personality issues, and chaotic lifestyles due to lifestyle and family difficulties.
The main activity that was used to help people, was – listen and to give advice.
The team did not use a process anymore, they used a framework to help them understand what to do in different situations. This framework developed from experience in the trial and systems thinking principles.
Taking the new approach with Sandra - what the officer would do now:
No recording on the council IT system was required, except for several sentences. Only one visit was needed by the officers and one by others to collect the rubbish.
The outcome was achieved with a significant reduction is actual work for the council. And a far better outcome for Sandra.
Comparing the Two Approaches
It is difficult to list down the differences between the two approaches, because even in this apparent simple situation, the circumstances are complex. But the description of the old and new approach highlights the difference in outcome for Sandra. Many of the demands coming in were more involved and complex than this one.
These are team insights that were then taken forward to design the new approach:
- We can make a big difference to people’s lives, and we have to stop making people’s lives worse.
- Before doing anything, we need to understand the whole picture about someone; listen, and never judge.
- Ignore departmental boundaries as much as possible.
- The officer who knows most should make the correct outcome happen.
- Take ownership of helping to solve the problem.
- Get support from others if you need to, or pass on ownership to someone else if that is the most appropriate action
- Take each case based on what matters to the person, do not follow a standard course of action.
The team analysed the root causes of the issues they dealt with, and they were: low level anxiety, depression, childhood issues, personality issues, and chaotic lifestyles due to lifestyle and family difficulties.
The main activity that was used to help people, was – listen and to give advice.
The team did not use a process anymore, they used a framework to help them understand what to do in different situations. This framework developed from experience in the trial and systems thinking principles.
Taking the new approach with Sandra - what the officer would do now:
- A complaint is made about rubbish in the garden.
- The officer who picks up the call, records down the location and then searches the system to find out more about Sandra.
- The officer visits Sandra and asks if he can come inside for a chat – but the officer does not mention the rubbish. The officer asks questions about how Sandra is able to pay the rent, and she talks for 20 minutes to the officer about all the problems she is having.
- The officer then asks Sandra if she has a problem with rubbish, she says yes. The officer sees that the cause of the problem is that she needs an extra bin. Then the officer asks how he can help her get rid of the rubbish. Sandra cries – it’s the first offer of help anyone has given her in weeks. They agree that the council will pick up the existing rubbish from the garden. And the officer then goes to his van and gets an extra bin and gives it to her.
- Sandra cannot thank the officer enough, she feels better for the rest of the day, and she does not shout at her child so much anymore. She feels more confident, and now has a hope that the council might help her in future, rather than give her more problems.
- The officer returns to the office and records a minimum amount of information against Sandra's record. Importantly, he records the issues of difficulty for Sandra.
No recording on the council IT system was required, except for several sentences. Only one visit was needed by the officers and one by others to collect the rubbish.
The outcome was achieved with a significant reduction is actual work for the council. And a far better outcome for Sandra.
Comparing the Two Approaches
It is difficult to list down the differences between the two approaches, because even in this apparent simple situation, the circumstances are complex. But the description of the old and new approach highlights the difference in outcome for Sandra. Many of the demands coming in were more involved and complex than this one.
An real example of Complexity - Tracey
Another case that the team came across was Tracey - A 22 year old woman complains of anti-social behaviour. The causes of her issues were to do with;
She had contacted the council a total of 30 times over the past two years.
Outcome – after three visits, her anxiety had reduced, we helped her gain her confidence. She did not need any more support, and she had started to look for work. She has no recorded calls to the council since then.
The outcome was achieved with a reduction by around 30% in actual work for the council. And a far better outcome for Tracey. She just needed someone to answer her questions, and begin to give her confidence in herself.
If you are interested in the detail of Tracey and our work with her listen below, (8 min audio)
- Immaturity about knowing what to do in situations most adults her age would know.
- Low level anxiety.
- Pressure from her father was distracting her focus.
She had contacted the council a total of 30 times over the past two years.
Outcome – after three visits, her anxiety had reduced, we helped her gain her confidence. She did not need any more support, and she had started to look for work. She has no recorded calls to the council since then.
The outcome was achieved with a reduction by around 30% in actual work for the council. And a far better outcome for Tracey. She just needed someone to answer her questions, and begin to give her confidence in herself.
If you are interested in the detail of Tracey and our work with her listen below, (8 min audio)
The Outcome of the Trial
The results recorded from the cases taken in the trial, using the new way of working are:
Structure
Adult Social Care, Mental Health and the Police located some of their staff in the new Hub - to take advantage of the integrated way of working. Inappropriate referrals reduced significantly because staff were able to communicate directly with each other face to face, before simply throwing the problem into a 'referral'.
Team and Management Approach
The team discovered a radically new way of working. In the old way, they all followed a common process. But in the new way, each officer had to understand and decide for themselves what course of action to take. At the start of the process this was very difficult for staff to comprehend, especially for the managers. I had to help them learn new techniques, and they had to gain confidence in their approach and risk. But, for each officer, there came a moment when they suddenly 'got it.'
We created a decision-making framework that helped the officers to structure how to make decisions.
Each person became part of a self-managing team to some extent.
Managers The managers had to experiment with new approaches that encouraged team learning. They also had to develop new ways of managing and keeping control using empowered and delegated decision-making. This was a challenge, as the old ways were disbanded. I helped managers to learn how to evaluate cases and officers performance. The manager had to relinquish their old methods of control. Often the managers would go out with newer officers, to observe and learn how officers worked with the framework.
A weekly session was created where everyone would give an overview of their work, learning was shared, and issues were aired.
The behaviour and culture of everyone in the department changed.
The results recorded from the cases taken in the trial, using the new way of working are:
- Visits out of the office are reduced by 50%.
- Letters are almost never sent anymore.
- Internal communication within the council has increased x4.
- Patrols have almost been eliminated, unless they are what is needed.
- Actual cost savings due to reduced activities between 33% - 42%.
- Repeat calls dropped to less than 10%.
- The public loved the new approach.
- The staff began to enjoy their work – it’s much better than being unpopular.
Structure
Adult Social Care, Mental Health and the Police located some of their staff in the new Hub - to take advantage of the integrated way of working. Inappropriate referrals reduced significantly because staff were able to communicate directly with each other face to face, before simply throwing the problem into a 'referral'.
Team and Management Approach
The team discovered a radically new way of working. In the old way, they all followed a common process. But in the new way, each officer had to understand and decide for themselves what course of action to take. At the start of the process this was very difficult for staff to comprehend, especially for the managers. I had to help them learn new techniques, and they had to gain confidence in their approach and risk. But, for each officer, there came a moment when they suddenly 'got it.'
We created a decision-making framework that helped the officers to structure how to make decisions.
Each person became part of a self-managing team to some extent.
Managers The managers had to experiment with new approaches that encouraged team learning. They also had to develop new ways of managing and keeping control using empowered and delegated decision-making. This was a challenge, as the old ways were disbanded. I helped managers to learn how to evaluate cases and officers performance. The manager had to relinquish their old methods of control. Often the managers would go out with newer officers, to observe and learn how officers worked with the framework.
A weekly session was created where everyone would give an overview of their work, learning was shared, and issues were aired.
The behaviour and culture of everyone in the department changed.
from We enforce to We help
Next is a video of an account of the project from a team member, 8 min
End of article
Below is a description of the approach that was used to undertake this transformation. The methodologies includes Design Thinking and Systems Thinking, incorporated into Service Design.
The Service Design Methodology
The approach that this piece of work took combined Design Thinking principles with Service Design and System Thinking, with a sprinkling of Lean. Each 'thinking' is woven into the overall method, so that in one morning, the conversations will always start with what matters to the end user, incorporate an end to end perspective, and talk about the real barriers int he organisation. We challenged everything.
The Service - Service design focuses on applying design thinking principles to a service, by embracing the needs of the 'customer.' In a local government service, the application of this approach is not quite the same as in a private organisation. The reason is in asking the question what os the service delivery? It has to be the actions of the officers to help someone to fix a problem. Therefore the innovative approach is applied to the whole service delivery approach. That has to include every element that is directly part of the delivery; rules and procedures, staff roles, measures, empowerment, and managers role. That may be why this case study may appear to be different to others.
The Plan was agreed with the client - but they had no experience of this type of approach, so I had show them that a fixed project management approach would be ineffective - the plan had to be part of Understand. But what might be interesting to the reader is that this is really about Transformative change. In this type of change, which is a complex wicked problem; part of the discovery is to find out where we were going to go. I say we, because this involved transforming peoples thinking as well as the service.
The team - Transforming thinking is something that happens when people decide to explore and accept other fundamental possibilities. So, the team that went through this had to be officers from the organisation, plus managers. They had to undergo the journey, and the only way to do that was for them to actually do it themselves.
My role as the consultant was as a facilitator, and as a coach. I would give them the right tools at the right time, and they would develop the outcomes. So, no nice clean diagrams from me, they were all generated by the team.
The managers - two of the managers were involved for about 1-2 days a week. They had to start by being part of the team, and they had to learn. Slowly over time they started to learn new ways of interacting with the team and allowing officers to come up with the solutions. The manager had to learn how to work with an empowered and self managing team. Whats the role of the manager when the team are self managing?
The Service - Service design focuses on applying design thinking principles to a service, by embracing the needs of the 'customer.' In a local government service, the application of this approach is not quite the same as in a private organisation. The reason is in asking the question what os the service delivery? It has to be the actions of the officers to help someone to fix a problem. Therefore the innovative approach is applied to the whole service delivery approach. That has to include every element that is directly part of the delivery; rules and procedures, staff roles, measures, empowerment, and managers role. That may be why this case study may appear to be different to others.
The Plan was agreed with the client - but they had no experience of this type of approach, so I had show them that a fixed project management approach would be ineffective - the plan had to be part of Understand. But what might be interesting to the reader is that this is really about Transformative change. In this type of change, which is a complex wicked problem; part of the discovery is to find out where we were going to go. I say we, because this involved transforming peoples thinking as well as the service.
The team - Transforming thinking is something that happens when people decide to explore and accept other fundamental possibilities. So, the team that went through this had to be officers from the organisation, plus managers. They had to undergo the journey, and the only way to do that was for them to actually do it themselves.
My role as the consultant was as a facilitator, and as a coach. I would give them the right tools at the right time, and they would develop the outcomes. So, no nice clean diagrams from me, they were all generated by the team.
The managers - two of the managers were involved for about 1-2 days a week. They had to start by being part of the team, and they had to learn. Slowly over time they started to learn new ways of interacting with the team and allowing officers to come up with the solutions. The manager had to learn how to work with an empowered and self managing team. Whats the role of the manager when the team are self managing?
understand
So, the first thing we did was to listen to demands:
Demand
From a design thinking and service design perspective starting with the outside-in - customer perspective is fundamental. I would like to detail the approach here for this type of service. Which is perhaps different to many of those others encounter. I understand several levels of 'depth'
1. The immediate user experience
2. The user feeling when interacting.
3. Understanding the customer, their immediate expectations and solutions.
4. Understanding the main problems the 'customer' is facing in achieving what thew came to me for.
5. All of the above, but extended to their current lives - plus the barriers they face, and what they would like me to help them with.
The video above of Tracey will demonstrate this depth.
Each level will produce a different action and outcome. In this work it is important to realise that I operate at level 5. So, the initial demand is often not the problem - it is other things that the council officer can help them with that surround the persons life.
The example of Tracey in the text above is a good example of this, where the team had to help her with her decision-making, maturity, and anxiety. That has nothing to do with the service that the council traditionally provide!
Understand the end to end work flow
We then started to map the flows of the forms that came in to the office. I showed the team how to do this, and they decided how they were going to complete the task. I facilitated and helped them to create flows that were readable.
Value - and waste reduction
We then looked at the flows and decided which of the activities were value and which were not. We did this because we wanted to focus on Value activities when we began the prototyping.
Using Lean techniques, what the team found was that only 10% of activities were creating value! And this was the beginning of the realisation that there was much to improve.
Performance - impact on the public Somehow the team had to understand how well they were doing as a service, and the only way is to measure the success from the customers perspective. We found this very difficult, as the demands were not transactional. In the end we measured how many people called again, and we also went and spoke to people to ask them if their issues had been resolved.
Demand
- listen to the demands coming in. The team did this themselves, and after two days they recorded down what they had found from the forms coming in, listening to phone calls, and listening to people coming in.
- The demands were categorised according to what they were.
From a design thinking and service design perspective starting with the outside-in - customer perspective is fundamental. I would like to detail the approach here for this type of service. Which is perhaps different to many of those others encounter. I understand several levels of 'depth'
1. The immediate user experience
2. The user feeling when interacting.
3. Understanding the customer, their immediate expectations and solutions.
4. Understanding the main problems the 'customer' is facing in achieving what thew came to me for.
5. All of the above, but extended to their current lives - plus the barriers they face, and what they would like me to help them with.
The video above of Tracey will demonstrate this depth.
Each level will produce a different action and outcome. In this work it is important to realise that I operate at level 5. So, the initial demand is often not the problem - it is other things that the council officer can help them with that surround the persons life.
The example of Tracey in the text above is a good example of this, where the team had to help her with her decision-making, maturity, and anxiety. That has nothing to do with the service that the council traditionally provide!
Understand the end to end work flow
We then started to map the flows of the forms that came in to the office. I showed the team how to do this, and they decided how they were going to complete the task. I facilitated and helped them to create flows that were readable.
Value - and waste reduction
We then looked at the flows and decided which of the activities were value and which were not. We did this because we wanted to focus on Value activities when we began the prototyping.
Using Lean techniques, what the team found was that only 10% of activities were creating value! And this was the beginning of the realisation that there was much to improve.
Performance - impact on the public Somehow the team had to understand how well they were doing as a service, and the only way is to measure the success from the customers perspective. We found this very difficult, as the demands were not transactional. In the end we measured how many people called again, and we also went and spoke to people to ask them if their issues had been resolved.
prototype & trial
The team members were split up into pairs. Their purpose was to learn new approaches and they achieved this by taking demands and try and do them in a new way. They were given a set of principles to follow.
The sequence of what they did is described in the article above. What they learned was discussed at the end of each day all together, and recorded on a large matrix on the wall. We used a combination of systems thinking in overall approach so we effectively started the prototype from a blank piece of paper.
After working this way with a few demands, the team's view of what they had to do was radically changing. They realised that by
Actively listening,- they would get very different information from people they were there to help and from other staff, we found out what really mattered to people. Understand.
Focus on value - we could cut out huge amounts of overlap with other departments. And we only recorded what we needed to record on IT. Lean techniques.
Outcomes - we did what people asked us to do, if it was reasonable. Previously they had done what the council had told them to do as a standard procedure. Customer centric.
Solutions - We searched for solutions that we would not normally be involved with, like give advice on how to deal with low level anxiety. Value.
Helped them - if we saw that we were going to push their level of need higher, we would use another approach. So, we would reduce the amount of fines we gave out if we thought that the person had a good reason to do what they were doing, and if they had no money.
The sequence of what they did is described in the article above. What they learned was discussed at the end of each day all together, and recorded on a large matrix on the wall. We used a combination of systems thinking in overall approach so we effectively started the prototype from a blank piece of paper.
After working this way with a few demands, the team's view of what they had to do was radically changing. They realised that by
Actively listening,- they would get very different information from people they were there to help and from other staff, we found out what really mattered to people. Understand.
Focus on value - we could cut out huge amounts of overlap with other departments. And we only recorded what we needed to record on IT. Lean techniques.
Outcomes - we did what people asked us to do, if it was reasonable. Previously they had done what the council had told them to do as a standard procedure. Customer centric.
Solutions - We searched for solutions that we would not normally be involved with, like give advice on how to deal with low level anxiety. Value.
Helped them - if we saw that we were going to push their level of need higher, we would use another approach. So, we would reduce the amount of fines we gave out if we thought that the person had a good reason to do what they were doing, and if they had no money.
implement
We worked together on how to implement this with their colleagues. The decision-making framework was then used by the manager to help coach individual officers to build up their competence and expertise.
Team Working
The manager and the staff created a weekly meeting, where officers would each talk about the work they had been doing, and monition issues that they had. The team would learn from this feedback and also help each other share ideas and problem solving.
This session also allowed the manager to get a good understanding of what the officers were doing and the challenges they face.
Implementation
The implementation plan and method was mostly developed by the original team members. They knew their colleagues well, and knew what they went through to develop this approach. The primary technique of developing others followed the approach of going out with an original team member. So the sequence was:
1. Background information about what we learned in the prototype and trial (1/2 day)
2. Going out with an experienced team member (mentor) for the day.
3. Structured reflection on the day before.
4. The newer officer tries out the approach whilst together with the mentor.
5. The cycle continues until the new officer is confident and competent.
I left at this point and they and the managers implemented the approach across the whole department.
Team Working
The manager and the staff created a weekly meeting, where officers would each talk about the work they had been doing, and monition issues that they had. The team would learn from this feedback and also help each other share ideas and problem solving.
This session also allowed the manager to get a good understanding of what the officers were doing and the challenges they face.
Implementation
The implementation plan and method was mostly developed by the original team members. They knew their colleagues well, and knew what they went through to develop this approach. The primary technique of developing others followed the approach of going out with an original team member. So the sequence was:
1. Background information about what we learned in the prototype and trial (1/2 day)
2. Going out with an experienced team member (mentor) for the day.
3. Structured reflection on the day before.
4. The newer officer tries out the approach whilst together with the mentor.
5. The cycle continues until the new officer is confident and competent.
I left at this point and they and the managers implemented the approach across the whole department.
Service design and systems thinking transforms a public sector service

Introduction
Enforcement services are recognised as those public sector services that are designed around stopping people from doing something; littering, noise, anti social behaviour are good examples.
The services are always backed by legislation that defines the limits of what is acceptable, and those in the service often see themselves as having to ‘police’ or defend something.
Typically, for most services this is a warning, then a fine. Interestingly it is often the case that staff wear uniforms of some type.
Below is an example from a Food Safety Team from England, using a service design, Lean and systems thinking approach to challenge their current way of working.
The Details
When looking at food safety if you ask them what their job is, it is to;
enforce food standards on restaurant owners.
They have the ability to fine, or even to take the owner to court, if they think it is appropriate. For the restaurant owner, the experience is never one that they enjoy - the officer suddenly turns up at my door, telling me that I am here to inspect you.
What Used to Happen
When the officer arrives, they put on a white outfit, and walk around the kitchen inspecting what they want to see. The restaurant owner just has to watch. And the officer usually has a list of items they expect to see; clean surfaces, training records & certificates, proof of inspections, and so on.
At the end of the visit the officer will go back to their office, and type up a reference document that lists all the items that failed the inspection. Each problem will include sections from the legislation, and a warning of when they should be completed. The tone of the letter is very standard and official - and the wording must be written assuming that the letter might be shown in court.
What They do Now
The same group of officers, after they have transformed their approach, did something very different. Firstly, they realised from a systemic perspective, that their purpose was to:
help restaurants create safe food - not to fulfil a pre-determined list of criteria.
Back in the office, there is the biggest change:
Enforcement services are recognised as those public sector services that are designed around stopping people from doing something; littering, noise, anti social behaviour are good examples.
The services are always backed by legislation that defines the limits of what is acceptable, and those in the service often see themselves as having to ‘police’ or defend something.
Typically, for most services this is a warning, then a fine. Interestingly it is often the case that staff wear uniforms of some type.
Below is an example from a Food Safety Team from England, using a service design, Lean and systems thinking approach to challenge their current way of working.
The Details
When looking at food safety if you ask them what their job is, it is to;
enforce food standards on restaurant owners.
They have the ability to fine, or even to take the owner to court, if they think it is appropriate. For the restaurant owner, the experience is never one that they enjoy - the officer suddenly turns up at my door, telling me that I am here to inspect you.
What Used to Happen
- A stern officer arrives suddenly in my restaurant.
- “Please give me a place I can change my clothes”
- I wait, and worry about all the things I have not got right in my kitchen.
- The officer comes into my kitchen all dressed in white, with a clip-board. They ignore me, and look into every corner of my kitchen.
- They ask me for my staff training records, and I have two new staff who have not done the training.
- After 30 minutes, they take me into my office, and they tell me what I am doing wrong.
- The inspector did not see what I was dong right, that I have been very busy this week, and that I am trying my best. I hate them, I try and hide things from them.
When the officer arrives, they put on a white outfit, and walk around the kitchen inspecting what they want to see. The restaurant owner just has to watch. And the officer usually has a list of items they expect to see; clean surfaces, training records & certificates, proof of inspections, and so on.
At the end of the visit the officer will go back to their office, and type up a reference document that lists all the items that failed the inspection. Each problem will include sections from the legislation, and a warning of when they should be completed. The tone of the letter is very standard and official - and the wording must be written assuming that the letter might be shown in court.
What They do Now
The same group of officers, after they have transformed their approach, did something very different. Firstly, they realised from a systemic perspective, that their purpose was to:
help restaurants create safe food - not to fulfil a pre-determined list of criteria.
- They now first phone me, and ask when it would be a good time to visit.
- They arrive, they get changed, and we have a conversation about what issues I am facing. I tell them about the two new staff, and how busy I have been.
- They go to the kitchen and simply watch what is going on.
- Then, we have a further conversation and they show my staff a few things that they ask about.
- The inspectors write down a few points that I should take care of, and ask me if I need any help with them.
Back in the office, there is the biggest change:
- Paperwork has reduced by 80%. We only record what we need we need to, and we don’t type formal letters to the restaurants.
- We are not interested in the old measures, so we don’t need to record each problem on the measures system.
- The number of activities we used to do in an inspection flow was 134, now it is11.
- The purpose has changed from checking, to helping people when they need help. Our motivation has gone right up - I enjoy my work.
- If a restaurant manager has a problem, they will now call up the inspector and ask them for advice.
Have a look at these videos to experience what it was like
As an enforcement officer, it is now up to me to decide what I do and how I do it, for each situation I find myself in. It is great to be able to put into practice my knowledge, and help people.
In the office we have regular sessions, where we discuss what were doing, and what techniques we have learned. If any of us ever need help, all of us are there at the end of the phone - but the most helpful person is my manager.
Enforce principles of working - Command & Control principles:
- We follow instructions
- We ignore the individual issues with the person
- This is just a job, managers dont like me.
Help me principles of working - Person centred principles:
- We understand the customer, and their problems
- We adapt and do the right thing for them
- I enjoy my job, it helps people, they like me.
Summary of performance measures
• Service improved from requiring special measures to excellent
• Service ethos changed from enforcement to helping
• Waste reduced by 75%
• Cost saving 24% overall
• Staff reduced by 2
• Nationally recognised transformation
• Customer feedback changed from suspicion to welcoming
The Method - Systems thinking and Service Design
The approach that was used was to take a team of inspectors and the manager through a series of stages of learning and prototyping - they started by understanding what mattered to the restaurant manager. They also mapped out all the activities that they took to complete a visit, it was 134 steps!
They then set about experimenting with a new purpose - to help the managers create safe food. The team realised they had little idea how to actually do that, so they worked with one restaurant, and then another, until they had learned a new set of techniques and approaches that became their new way of working. They discarded those activities that they deemed not necessary.
The Implications
Think of those public services that are 'enforcement' - that fine, chase, force people to do certain things. Imagine what would be the implications to the community if those services, instead of
we enforce became we help??????
The difference was so great, that an article was published by the Chartered Institute of Environmental Health. You can read it here.
Design thinking, Service design and Systems thinking
If you want to know more about the detail of the design and systems thinking methodology used, it is described in this section...
The approach that this piece of work took combined Design Thinking principles with Service Design and System Thinking. Each 'thinking' is woven into the overall method, so that in one morning, the conversations will always start with what matters to the end user, and incorporate an end to end perspective. We challenged everything.
The Plan was agreed with the client - but they already had experience of this type of approach, and they know that they could not rely on a fixed outcome - it had to be part of the Understand. But what might be interesting to the reader is that this is really about Transformative change. In this type of change, which is a wicked problem; part of the discovery is to find out where we were going to go. I say we, because this involved transforming peoples thinking as well as the service.
The team - Transforming thinking is something that happens when people decide to explore and accept other possibilities. So, the team that went through this had to be officers from the organisation, plus a manager. They had to undergo the journey, and the only way to do that was for them to actually do it themselves.
My role as the consultant was as a facilitator, and as a coach. I would give them the right tools at the right time, and they would develop the outcomes. So, no nice clean diagrams form me, they were all generated by the team.
The managers - two of the managers were involved for about 1-2 days a week. They had to start by being part of the team, and they had to learn. Slowly over time they started to learn new ways of interacting with the team and allowing officers to come up with the solutions. The manager had to learn how to work with an empowered and self managing team. Whats the role of the manager when the team are self managing?
The Plan was agreed with the client - but they already had experience of this type of approach, and they know that they could not rely on a fixed outcome - it had to be part of the Understand. But what might be interesting to the reader is that this is really about Transformative change. In this type of change, which is a wicked problem; part of the discovery is to find out where we were going to go. I say we, because this involved transforming peoples thinking as well as the service.
The team - Transforming thinking is something that happens when people decide to explore and accept other possibilities. So, the team that went through this had to be officers from the organisation, plus a manager. They had to undergo the journey, and the only way to do that was for them to actually do it themselves.
My role as the consultant was as a facilitator, and as a coach. I would give them the right tools at the right time, and they would develop the outcomes. So, no nice clean diagrams form me, they were all generated by the team.
The managers - two of the managers were involved for about 1-2 days a week. They had to start by being part of the team, and they had to learn. Slowly over time they started to learn new ways of interacting with the team and allowing officers to come up with the solutions. The manager had to learn how to work with an empowered and self managing team. Whats the role of the manager when the team are self managing?
Understand
Understand is the analysis of the current system, its performance and the impact on the customer. The customer being the restaurant owner.
Systems thinking - The start of the process has to be to ask why are we here - our purpose? Design thinking - And then we have to understand HOW we achieve this purpose from an outside in perspective. Then we can truly get the customer experience, fully in our mind. In this case we were not able to do this until the next stage, this is because this work is so complex and deep, that it was only by trying to design a prototype did we truly understand what mattered to the owners of restaurants.
The customer journey, in this example, translates into the what matters to the owner. So journey maps were not appropriate.
Design thinking - The team spend a few days developing a workflow map, that contained each activity for a typical inspection. This map is only useful if it tells us something. So, we identified the value and waste.
Systems thinking - The start of the process has to be to ask why are we here - our purpose? Design thinking - And then we have to understand HOW we achieve this purpose from an outside in perspective. Then we can truly get the customer experience, fully in our mind. In this case we were not able to do this until the next stage, this is because this work is so complex and deep, that it was only by trying to design a prototype did we truly understand what mattered to the owners of restaurants.
The customer journey, in this example, translates into the what matters to the owner. So journey maps were not appropriate.
Design thinking - The team spend a few days developing a workflow map, that contained each activity for a typical inspection. This map is only useful if it tells us something. So, we identified the value and waste.
Systems thinking - 8 value steps, and 160 waste steps!!! The team were stunned. I kept this information until we moved to prototyping.
Systems thinking - we had to ask ourselves how effective the current system was? The answer was, we didn't know. But we do know that owners do not like to see us, and they try and hide bad practice from us.
Systems thinking - we had to ask ourselves how effective the current system was? The answer was, we didn't know. But we do know that owners do not like to see us, and they try and hide bad practice from us.
Prototype & learning
With a non-transactional workflow, it is not easy to see a new way forward. So, I had to do some work to get the creative juices flowing. These are officers who have had 'enforcement' drummed into them, for years. So...
Design thinking - On day one, the team had to learn to learn; about chefs, their behaviours, and attitudes. So, they had to go to a restaurant kitchen, stand int he corner, and learn. On their return one group said that it was really interesting... A good start. We worked on that.
The next day they went out to learn some more. They all went to a burger van, and talked to the owner - asking open questions.
Background - This owner had a poor safety record; he had been asked to replace the floor and put in hot water. But had never done this.
Learning - they learned that this man worked 7 days a week, sometimes making no money. Exhausted at the end of the day. He cared that his customers remained safe. The team were a little confused as to why we were spending time doing this..? We asked him if we could come tomorrow?
Learning - we saw that he was using his spatula for both cooked meats and fresh meat. Not good - but we did not say anything to him. - we were only allowed to learn, not do anything.
Design thinking - The teams task was now to learn, but also to experiment with anything that they thought was useful to help create safe food.
What we did - the next day, on the way to see him, we bought a spatula. When we arrived, he said hello, and gave him the spatula. Guess what he did - after a pause his eyes moistened. No-one had ever done anything like that before. Especially not a food safety inspector! He transformed into a welcoming, human being. He chatted, opened up, and was very friendly.
Learning - we have learned the secret that has been eluding us. We have now understood how to engage with people. This was the first breakthrough.
Design thinking - we now wanted to help him understand how poor he was at food preparation. But the team were not allowed to tell him in ther old way, something else had to happen.
What we did - the team designed a graph with all the burger van type business on, and the axis showed each of the businesses from good to poor. We coloured in the poor section in red. We turned up to visit him, was as we approached, he came out, and led us to his van. He offered us all a drink. Over a conversation, we asked him; "how well do you make safe food?" the answer was; oh, I a not great but not as bad as most people."
We then asked him to point to where he thought he was on the graph. Then we showed him where his business really was. And we said nothing. His eyes started to stare again. We continued a conversation and left.
What we did - after a few days, we returned to learn. Again, he came out and led us to his van, he wanted to show us something. He had fitted a new floor, and he had installed hot water!! iThe time, it was the teams turn to have watery eyes. He was so proud! He had done something the inspectors had asked him to do time and time again, over several years.
Learning - the second secret the team learned, was that when you listen, and engage with someone, and treat them ike a human, they respond cooperatively.
Design thinking - On day one, the team had to learn to learn; about chefs, their behaviours, and attitudes. So, they had to go to a restaurant kitchen, stand int he corner, and learn. On their return one group said that it was really interesting... A good start. We worked on that.
The next day they went out to learn some more. They all went to a burger van, and talked to the owner - asking open questions.
Background - This owner had a poor safety record; he had been asked to replace the floor and put in hot water. But had never done this.
Learning - they learned that this man worked 7 days a week, sometimes making no money. Exhausted at the end of the day. He cared that his customers remained safe. The team were a little confused as to why we were spending time doing this..? We asked him if we could come tomorrow?
Learning - we saw that he was using his spatula for both cooked meats and fresh meat. Not good - but we did not say anything to him. - we were only allowed to learn, not do anything.
Design thinking - The teams task was now to learn, but also to experiment with anything that they thought was useful to help create safe food.
What we did - the next day, on the way to see him, we bought a spatula. When we arrived, he said hello, and gave him the spatula. Guess what he did - after a pause his eyes moistened. No-one had ever done anything like that before. Especially not a food safety inspector! He transformed into a welcoming, human being. He chatted, opened up, and was very friendly.
Learning - we have learned the secret that has been eluding us. We have now understood how to engage with people. This was the first breakthrough.
Design thinking - we now wanted to help him understand how poor he was at food preparation. But the team were not allowed to tell him in ther old way, something else had to happen.
What we did - the team designed a graph with all the burger van type business on, and the axis showed each of the businesses from good to poor. We coloured in the poor section in red. We turned up to visit him, was as we approached, he came out, and led us to his van. He offered us all a drink. Over a conversation, we asked him; "how well do you make safe food?" the answer was; oh, I a not great but not as bad as most people."
We then asked him to point to where he thought he was on the graph. Then we showed him where his business really was. And we said nothing. His eyes started to stare again. We continued a conversation and left.
What we did - after a few days, we returned to learn. Again, he came out and led us to his van, he wanted to show us something. He had fitted a new floor, and he had installed hot water!! iThe time, it was the teams turn to have watery eyes. He was so proud! He had done something the inspectors had asked him to do time and time again, over several years.
Learning - the second secret the team learned, was that when you listen, and engage with someone, and treat them ike a human, they respond cooperatively.
TEST
Wen the team had got over their 'enforcement' mindset and learned the fundamental principles of a new way of working, they proceeded to develop a new approach using these principles:
- understand the owner as a person and the situation they are in.
- find ways of helping the owner to see things about their food preparation.
- discuss with them ways forward.
- learn and apply, learn and apply, learn and apply...
After a few weeks, they had learned a new approach that was working.
The new workflow - I asked the team to create a new workflow, with only the 8 value steps in - no waste.And they got quite close. Letters were ditched, no reports, and no unnecessary recording on IT systems. The result was two visits a day were normal, rather than one.
- understand the owner as a person and the situation they are in.
- find ways of helping the owner to see things about their food preparation.
- discuss with them ways forward.
- learn and apply, learn and apply, learn and apply...
After a few weeks, they had learned a new approach that was working.
The new workflow - I asked the team to create a new workflow, with only the 8 value steps in - no waste.And they got quite close. Letters were ditched, no reports, and no unnecessary recording on IT systems. The result was two visits a day were normal, rather than one.
Systems thinking - the mindset was the key to everything in this work. As they learned, they unlearned. One of the greatest frameworks that created the old 'enforce' mindset, was the legislation. They would use the wording of the legislation to act as their bedrock, and as an the reason to justify their actions and behaviour.
I had to show them, by working with the owners, that the legislation had to be used:
as a guide to safe food preparation, not as a prescriptive set of words.
That was tough to do, but it worked. They finally had the courage to stand on their own two feet as people, who could help people create safe food.
I had to show them, by working with the owners, that the legislation had to be used:
as a guide to safe food preparation, not as a prescriptive set of words.
That was tough to do, but it worked. They finally had the courage to stand on their own two feet as people, who could help people create safe food.
implement
Preparation - Everything about what they did before had to be changed. So procedures, IT systems, measures and tools had to be created.
Showing others - The task of teaching others, then began, and the team realised that they could not just tell their fellow inspectiors what they had to do, they had to show them and work with them. It took time, lots of time. But it worked.
Two members of staff did not like the new way of working, so they decided to leave.
Showing others - The task of teaching others, then began, and the team realised that they could not just tell their fellow inspectiors what they had to do, they had to show them and work with them. It took time, lots of time. But it worked.
Two members of staff did not like the new way of working, so they decided to leave.
Understanding complexity and then applying that to dealing with customers is critical to true service and systems design

Interesting to read this article in the guardian that the issues with the NHS are not just about ‘fixing people’ when they are unwell. But that loneliness has a large impact on people well-being, demonstrated in the figures for 50% less life expectancy to those that are lonely.
Analysis
When I did some work in the NHS, and we looked at the demand into hospitals and also helping people in the community - going to the GP, or after they have left the hospital. Something about what we were learning about the demand seemed to need further analysis. It is easy to treat different types of demand as common categories - broken leg, diabetes, etc. But when we looked at the time taken to help people get back to a normal life, there was great variation in the resources and time used with the same category.
Complexity
We discovered that certain people absorbed far more resources, visit their GP, or were admitted to hospital far more than others. These people often had a level of complexity to their situation that was not obviously identified when looking at their records. When we analysed a cohort of patients it was obvious to attribute age to the cause of increasing complexity. But looking at each person in detail we discovered the causes were various. And what was the highest cause of complexity? Loneliness.
It surprised everyone around us, that this was the result of the analysis. And how well had this health trust geared itself up to respond to this problem? Well, apart from having weekly public social gatherings, the problem was not on anyones radar as being important.
What we did
What we did was to tackle the loneliness head on, taking a cohort of people that were in the health system. The result was that their interaction with the health system went down, in some cases so dramatically, that they stopped seeing anyone in the NHS.
Its how we view our demand
Prior to this analysis, the NHS had been looking at demand using categories that they had created and defined each person. However, this is a good example of looking at a complex system, and applying system thinking principles and techniques to its analysis and design. Then the demand is understood outside-in, how people interact with the system, and what matters to them. This simple approach allows an organisation to fundamentally alter their approach to how they deal with people, so that their resourcrs are cut by 30%, and the outcomes are improved. Predefined categories tend to limit our ability to really understand our organisation and the workflow clearly.
Analysis
When I did some work in the NHS, and we looked at the demand into hospitals and also helping people in the community - going to the GP, or after they have left the hospital. Something about what we were learning about the demand seemed to need further analysis. It is easy to treat different types of demand as common categories - broken leg, diabetes, etc. But when we looked at the time taken to help people get back to a normal life, there was great variation in the resources and time used with the same category.
Complexity
We discovered that certain people absorbed far more resources, visit their GP, or were admitted to hospital far more than others. These people often had a level of complexity to their situation that was not obviously identified when looking at their records. When we analysed a cohort of patients it was obvious to attribute age to the cause of increasing complexity. But looking at each person in detail we discovered the causes were various. And what was the highest cause of complexity? Loneliness.
It surprised everyone around us, that this was the result of the analysis. And how well had this health trust geared itself up to respond to this problem? Well, apart from having weekly public social gatherings, the problem was not on anyones radar as being important.
What we did
What we did was to tackle the loneliness head on, taking a cohort of people that were in the health system. The result was that their interaction with the health system went down, in some cases so dramatically, that they stopped seeing anyone in the NHS.
Its how we view our demand
Prior to this analysis, the NHS had been looking at demand using categories that they had created and defined each person. However, this is a good example of looking at a complex system, and applying system thinking principles and techniques to its analysis and design. Then the demand is understood outside-in, how people interact with the system, and what matters to them. This simple approach allows an organisation to fundamentally alter their approach to how they deal with people, so that their resourcrs are cut by 30%, and the outcomes are improved. Predefined categories tend to limit our ability to really understand our organisation and the workflow clearly.
Public sector data protection should allow us to share data - not hinder us
Data sharing, often a major stumbling block to joined-up working in the public sector. How to use a systemic approach to thinking about the problem and delivering a different and far easier solution.
Lets start with a real case study and define the problem that this organisation had.
The Problem
I came across a new data sharing issue in a new Hub we were redesigning recently. In this situation local government Council staff were newly sitting next to and working with the Police. The question was:
How do we now share information between us?
This was a project started to develop the workflows, policies and practice in the Hub. The Police, and Council front line staff were in a multi-disciplinary change team, and the managers were connected to that team.
What the Police Did
If anyone works with the Police you will find that they have a quite different way of making decisions than any other type of organisation. In the situation with the Hub, they made a local decision to share data in the way that supervisors on the ground thought was reasonable. However, when they went and asked their Data Controller, and the Controller replied they could not share any of the data. As simple as that! The Police then spent the rest of the three months in this position - frustrated, but unable to proceed.
The Standard Solution
As is usual, the purpose has to be defined or understood. It will be defined by managers, and may be defined something like;
we need a set of rules on how to legally share data between us, that protects people and allows us to work together efficiently.
This is the usual approach in most organisations to solve a problem like this. They will ask a consultant with analytical knowledge to look at this as a project and study the data. They also need to be fully aware of the legislation, so they ask the Data Controller and get a copy of the Data Protection Act, and read it in detail.
This consultant then takes the data types from a data analyst, and attempts to categorise the data into the categories that make sense, and that show different levels of risk. They would look at the job roles of all the people involved and attempt to make a judgement as to the data they are required to view and why. And engage with the Data Controller and put all the collected findings on the table.
The outcome will be a report, that will be approved, and then circulated down through the hierarchy - as each manager makes sure that their particular concern or point is contained in the final report. In some cases this step in the process can take many months and the problem is seen as:
the needs of different stakeholders, which must be taken into account.
Staff groups are put on a schedule to listen to their managers tell them what the new rules are.
The Systemic Approach
Understand
Again, the first step that has to happen is that the problem has to be understood. This is done by going to where the work is. The change team listen to demands coming into the Hub, by actually listening to the conversations. They have to understand the whole problem and what matters to the person making the demand.
The purpose they define for the sharing of information remains undefined.
Redesign.
The next step, after listening to the demand, is to undertake the work - by just doing the work that matters to fix the problem - together with the person.
The Data
So what of the data sharing? Well, the example above is looked at by the team, and the key information that was needed to provide the knowledge required to solve the problem is written down.
The above process is repeated several times, until the team understand enough about the demands and the knowledge. They might do 20 or more demands.
Then the team sit together and analyse what knowledge is needed, and where it is usually held. Interestingly it is quite often held in peoples memories rather than simply in a computer.
The purpose they define for the sharing of information now emerges from the evidence.
The Outcome
This analysis is then used to define the agreement on the sharing of knowledge. If a manager does not like this, or wants to add other rules, then they have to work with the team to demonstrate that the evidence proves that this change should be made.
The word data is not included in any document or discussion. The purpose of this exercise is the sharing of knowledge
From a systems thinking perspective, what is important in this problem is not about data, but pertinent information regarding a council officer about to visit the property of someone. As soon as you make it data you have entered the world of concepts and ideas. Systems thinking has to be firmly rooted in the reality of what the the system is really about.
The solution was surprisingly easy, focus on the information - not the data. When there is a new demand, and the council officer wants to know about the what we know about the person making the demand, then they ask a police officer in-front of a computer if there are any issues I need to be aware of when I visit Mr. Smith.
The officer could respond with;
After the demands were understood, It took about two weeks to define, and make into a workshop for staff.
The Difference Between Systems Thinking and our Usual Approach?
Point 1 - there is are no stakeholder needs, as the person and the demand defines the need.
Point 2 - there is no inflexible set of rules that applies to certain categories of demands.
Point 3 - the managers do not initially define the outcome, the evidence does. Then the managers agree the analysis the team undertook.
What is needed is not the data, its the knowledge I need before the visit and during the process. This real need by-passes all data arguments, as the real basis of data sharing is the sharing of knowledge. The sharing of data can be a side issue to the main principle, that is often used when sharing is between people far away from each other and who are unable to collaborate. If you can collaborate with your colleague in the other service, then the sharing becomes one of knowledge - and a different and much easier problem to fix.
In addition, this approach supports the front line staff and is flexible to every situation. So no detailed procedures or rules are necessary - just the creation of a set of principles to work to in a framework that front-line staff can be coached to use.
This is an real example of using systems thinking to the problem of data sharing. The problem is redefined from data to knowledge - which is should have always been in the first place, if the legislation had been looked at from a systemic perspective then maybe the problem so many public sector organisations are having would be made alot easier.
The data protection act in the UK is actually written to help data sharing and to prevent private organisations from marketing our data. But we tend to see it only as the method of restricting communication. Certainly those who wrote it made a big error in the way that it puts across the central concept of what it is about. But, it really does focus on DATA, and in public sector operations we are far more interested in information.
Lets start with a real case study and define the problem that this organisation had.
The Problem
I came across a new data sharing issue in a new Hub we were redesigning recently. In this situation local government Council staff were newly sitting next to and working with the Police. The question was:
How do we now share information between us?
This was a project started to develop the workflows, policies and practice in the Hub. The Police, and Council front line staff were in a multi-disciplinary change team, and the managers were connected to that team.
What the Police Did
If anyone works with the Police you will find that they have a quite different way of making decisions than any other type of organisation. In the situation with the Hub, they made a local decision to share data in the way that supervisors on the ground thought was reasonable. However, when they went and asked their Data Controller, and the Controller replied they could not share any of the data. As simple as that! The Police then spent the rest of the three months in this position - frustrated, but unable to proceed.
The Standard Solution
As is usual, the purpose has to be defined or understood. It will be defined by managers, and may be defined something like;
we need a set of rules on how to legally share data between us, that protects people and allows us to work together efficiently.
This is the usual approach in most organisations to solve a problem like this. They will ask a consultant with analytical knowledge to look at this as a project and study the data. They also need to be fully aware of the legislation, so they ask the Data Controller and get a copy of the Data Protection Act, and read it in detail.
This consultant then takes the data types from a data analyst, and attempts to categorise the data into the categories that make sense, and that show different levels of risk. They would look at the job roles of all the people involved and attempt to make a judgement as to the data they are required to view and why. And engage with the Data Controller and put all the collected findings on the table.
The outcome will be a report, that will be approved, and then circulated down through the hierarchy - as each manager makes sure that their particular concern or point is contained in the final report. In some cases this step in the process can take many months and the problem is seen as:
the needs of different stakeholders, which must be taken into account.
Staff groups are put on a schedule to listen to their managers tell them what the new rules are.
The Systemic Approach
Understand
Again, the first step that has to happen is that the problem has to be understood. This is done by going to where the work is. The change team listen to demands coming into the Hub, by actually listening to the conversations. They have to understand the whole problem and what matters to the person making the demand.
The purpose they define for the sharing of information remains undefined.
Redesign.
The next step, after listening to the demand, is to undertake the work - by just doing the work that matters to fix the problem - together with the person.
The Data
So what of the data sharing? Well, the example above is looked at by the team, and the key information that was needed to provide the knowledge required to solve the problem is written down.
The above process is repeated several times, until the team understand enough about the demands and the knowledge. They might do 20 or more demands.
Then the team sit together and analyse what knowledge is needed, and where it is usually held. Interestingly it is quite often held in peoples memories rather than simply in a computer.
The purpose they define for the sharing of information now emerges from the evidence.
The Outcome
This analysis is then used to define the agreement on the sharing of knowledge. If a manager does not like this, or wants to add other rules, then they have to work with the team to demonstrate that the evidence proves that this change should be made.
The word data is not included in any document or discussion. The purpose of this exercise is the sharing of knowledge
From a systems thinking perspective, what is important in this problem is not about data, but pertinent information regarding a council officer about to visit the property of someone. As soon as you make it data you have entered the world of concepts and ideas. Systems thinking has to be firmly rooted in the reality of what the the system is really about.
The solution was surprisingly easy, focus on the information - not the data. When there is a new demand, and the council officer wants to know about the what we know about the person making the demand, then they ask a police officer in-front of a computer if there are any issues I need to be aware of when I visit Mr. Smith.
The officer could respond with;
- no problem,
- maybe you should go with a colleague,
- the mother has difficulties talking to a official,
- there may be someone staying there illegally,
- talk to Jason, he knows a bit about this family,
- a police officer will go with you as it might be tricky,
- dont go - lets have a conversation...
After the demands were understood, It took about two weeks to define, and make into a workshop for staff.
The Difference Between Systems Thinking and our Usual Approach?
Point 1 - there is are no stakeholder needs, as the person and the demand defines the need.
Point 2 - there is no inflexible set of rules that applies to certain categories of demands.
Point 3 - the managers do not initially define the outcome, the evidence does. Then the managers agree the analysis the team undertook.
What is needed is not the data, its the knowledge I need before the visit and during the process. This real need by-passes all data arguments, as the real basis of data sharing is the sharing of knowledge. The sharing of data can be a side issue to the main principle, that is often used when sharing is between people far away from each other and who are unable to collaborate. If you can collaborate with your colleague in the other service, then the sharing becomes one of knowledge - and a different and much easier problem to fix.
In addition, this approach supports the front line staff and is flexible to every situation. So no detailed procedures or rules are necessary - just the creation of a set of principles to work to in a framework that front-line staff can be coached to use.
This is an real example of using systems thinking to the problem of data sharing. The problem is redefined from data to knowledge - which is should have always been in the first place, if the legislation had been looked at from a systemic perspective then maybe the problem so many public sector organisations are having would be made alot easier.
The data protection act in the UK is actually written to help data sharing and to prevent private organisations from marketing our data. But we tend to see it only as the method of restricting communication. Certainly those who wrote it made a big error in the way that it puts across the central concept of what it is about. But, it really does focus on DATA, and in public sector operations we are far more interested in information.

Just when the news of the Scottish police centralisation of call handlng has shown that there are significant problems with this approach, Mike Penning, a home office minister has stated that the combining of three emergency services will bring significant benefits. This will bring in economies of scale with the sharing of back office services. Efficiency jsut drops out as the answer, doesn't it?
This is not the place to resort to egoistically stating one view over another. No, its time to realise that we, as a nation, relish in stating the obvious. At least, we all think we are stating the obvious, and each of us comes up with the solution that makes sense. Maybe its about time that we stood back a little, and recognise that we keep returning to this style of behaviour like flies around a light bulb.
Its obvious that covering a pan that is boiling over, to stop it from spilling its hot contents is a solution to a problem. But the better solution is to switch off the gas.
Transformation is about doing different things, not doing the same things differently. It is about looking at what we have been doing, and choosing to approach problems from different perspectives. I would suggest to Mike Penning that his good idea, based on common sense, just before he commits millions, to just do a few simple things:
1. Get someone to help you learn how the current system works. Understand its underlying assumptions. Discover the root cause of the issues.
2. Start with a better set of assumptions, and apply a different logic to the problem you have to solve.
3. Start to redesign the system, so that the problem's root causes are eliminated.
4. You end up with a system that works differently than before, will cost less, and performs better.
You need someone to show you how to do it, because it is very difficult to see the system we are in differently, without someone to help us.
Its actually not difficult, and will only take a few weeks to do 1 and 2, but it will save milllions.
Remember this from 2010? The principles were exactly the same...
“FiRecontrol was a project established under the previous Labour Government, and is now being scrapped because it does not work.
“This project has wasted millions of pounds of public money as well as thousands of firefighter hours in trying to bring it to completion.
This is a plea for trying something different, so my tax money will not be wasted again.
I just want to add this about Ian Duncan Smith and Universal Credits. Its the same principle as sharing control centres, related to a process:
"This is the man who is the chief architect of the Universal Credit, which was supposed to have been rolled out in October 2013, and in March 2016 has been rolled out to the grand total of 141,100 people - and by "people", I mean "single men without dependents", the only group whose claims are simple enough to be processed on the Universal Credit."
Stephen Bush, New Statesman
Good grief, look at this! facebook page about universal credit
This is not the place to resort to egoistically stating one view over another. No, its time to realise that we, as a nation, relish in stating the obvious. At least, we all think we are stating the obvious, and each of us comes up with the solution that makes sense. Maybe its about time that we stood back a little, and recognise that we keep returning to this style of behaviour like flies around a light bulb.
Its obvious that covering a pan that is boiling over, to stop it from spilling its hot contents is a solution to a problem. But the better solution is to switch off the gas.
Transformation is about doing different things, not doing the same things differently. It is about looking at what we have been doing, and choosing to approach problems from different perspectives. I would suggest to Mike Penning that his good idea, based on common sense, just before he commits millions, to just do a few simple things:
1. Get someone to help you learn how the current system works. Understand its underlying assumptions. Discover the root cause of the issues.
2. Start with a better set of assumptions, and apply a different logic to the problem you have to solve.
3. Start to redesign the system, so that the problem's root causes are eliminated.
4. You end up with a system that works differently than before, will cost less, and performs better.
You need someone to show you how to do it, because it is very difficult to see the system we are in differently, without someone to help us.
Its actually not difficult, and will only take a few weeks to do 1 and 2, but it will save milllions.
Remember this from 2010? The principles were exactly the same...
“FiRecontrol was a project established under the previous Labour Government, and is now being scrapped because it does not work.
“This project has wasted millions of pounds of public money as well as thousands of firefighter hours in trying to bring it to completion.
This is a plea for trying something different, so my tax money will not be wasted again.
I just want to add this about Ian Duncan Smith and Universal Credits. Its the same principle as sharing control centres, related to a process:
"This is the man who is the chief architect of the Universal Credit, which was supposed to have been rolled out in October 2013, and in March 2016 has been rolled out to the grand total of 141,100 people - and by "people", I mean "single men without dependents", the only group whose claims are simple enough to be processed on the Universal Credit."
Stephen Bush, New Statesman
Good grief, look at this! facebook page about universal credit

Isn't it a fact that many people can talk at length about the reasons as to why we, as managers in organisations, are always striving to create a great organisation. We can list the top reasons as to why we need to change, and another list of what needs to change. How about a list showing the characteristics of successful leaders? Does anyone like to count the number of books on this subject?
Yet, when we actually look at what works, and what does not work, actually watch managers manage, what is the one thing that underpins what is REALLY stopping us. Is not the answer, that we all actually know deep down, is us - our own fear of the unknown - of stepping out of our zones of comfort? Its easy to say that we must become bold, etc. Its another to actually feel the wind of uncertainty grip our chests.
Which manager is prepared to take the risk of a new approach, when they are being measured on success, by a room full of grim faced, suited stalwarts. Isn't it easier to follow the tried and tested approaches, that were developed about 80 years ago?
Our real barriers are all in our heads.
Its not easy, but the first step is to recognise our limitations, and be prepared to challenge them. Then find an approach and the right people who share your vision. Then you have a chance to succeed...
Yet, when we actually look at what works, and what does not work, actually watch managers manage, what is the one thing that underpins what is REALLY stopping us. Is not the answer, that we all actually know deep down, is us - our own fear of the unknown - of stepping out of our zones of comfort? Its easy to say that we must become bold, etc. Its another to actually feel the wind of uncertainty grip our chests.
Which manager is prepared to take the risk of a new approach, when they are being measured on success, by a room full of grim faced, suited stalwarts. Isn't it easier to follow the tried and tested approaches, that were developed about 80 years ago?
Our real barriers are all in our heads.
Its not easy, but the first step is to recognise our limitations, and be prepared to challenge them. Then find an approach and the right people who share your vision. Then you have a chance to succeed...

So, the Scottish Police centralisation of calls is being put on hold. What is the problem? The problem is that we as decision-makers love to use the same clever principles to make decisions, that on reflection, seem to be plausible.
The problem is that the police service relies heavily on calls into the system. These calls arrive at all times of the day, with varied frequency over the day. At small sites the cost of managing these call handlers, arranging their shifts, and preparing for holidays and sickness is a challenge. So, the solution is to get them all from the smaller sites, put them in a big building, and connect them with technology, back to their original locations. Then, maybe we can recruit cheaper grade staff to answer the calls, based on best practice CRM systems. If we can call India when we talk to a bank, surely its a no-brainer?
It all makes sense to a decision-maker, who is being pushed to make savings, the like that have never been experienced by that leader in the lifetime of the service. The logic and the maths make perfect sense.
The reality is this. The demand that comes in is often complex and fails to follow a pre-determined pattern to resolve. That seemingly simple call about a Facebook spat can turn nasty if not dealt with according to the unique circumstances of what matters to that particular caller. The history of conflict within the facebook issue, shows that those invovled have been warring for some time.
Then, if we do pass on the call to a division, it gets categorised, prioritised, and then sits in a queue until someone in a locality picks it up and reads it. They read what was written by the call handler, not what was actually said, not understanding the intonation in the voice, not hearing the confused shy vulnerable message struggling to be heard over and above the categorisation they are being forced to be placed in.
The call-handler is trained to push away calls deemed not for the police. The unintended consequence is often an escalatin of the incident, until it becomes necessary to respond to with greater attention.
The locality the call eventually gets to, need to call the caller back, to obtain more information that was not detailed on the record. The phone number is tried several times, before contact is remade. The officer who can really help understand and help the caller, finally talks to the person with the problem, and then finally starts the value work of sorting out the problem. Hopefuly it is not too late by then, but it has caused a load of waste activity to ripple through the organisation.
One day someone will come up with the bright idea of in the first instance, getting the caller to talk directly to the person who can help them resolve the problem, and that same manager who set up the big building full of call handlers will find that the cost of doing this is considerably less than the old way. And, as a by product, the service is markedly improved.
It is what happens to all such contact centres if they are analysed in the right way, but it takes so many of us to make the expensive mistake before we learn that lesson. By that time, a new manager has taken the reigns, and they have a great idea to solve the cost of different localities taking their own calls... The wheel goes round again.
Take a systems thinking approach to this problem, and the right solution will be clear.
Scottish policing article from Ian Wiggett
The problem is that the police service relies heavily on calls into the system. These calls arrive at all times of the day, with varied frequency over the day. At small sites the cost of managing these call handlers, arranging their shifts, and preparing for holidays and sickness is a challenge. So, the solution is to get them all from the smaller sites, put them in a big building, and connect them with technology, back to their original locations. Then, maybe we can recruit cheaper grade staff to answer the calls, based on best practice CRM systems. If we can call India when we talk to a bank, surely its a no-brainer?
It all makes sense to a decision-maker, who is being pushed to make savings, the like that have never been experienced by that leader in the lifetime of the service. The logic and the maths make perfect sense.
The reality is this. The demand that comes in is often complex and fails to follow a pre-determined pattern to resolve. That seemingly simple call about a Facebook spat can turn nasty if not dealt with according to the unique circumstances of what matters to that particular caller. The history of conflict within the facebook issue, shows that those invovled have been warring for some time.
Then, if we do pass on the call to a division, it gets categorised, prioritised, and then sits in a queue until someone in a locality picks it up and reads it. They read what was written by the call handler, not what was actually said, not understanding the intonation in the voice, not hearing the confused shy vulnerable message struggling to be heard over and above the categorisation they are being forced to be placed in.
The call-handler is trained to push away calls deemed not for the police. The unintended consequence is often an escalatin of the incident, until it becomes necessary to respond to with greater attention.
The locality the call eventually gets to, need to call the caller back, to obtain more information that was not detailed on the record. The phone number is tried several times, before contact is remade. The officer who can really help understand and help the caller, finally talks to the person with the problem, and then finally starts the value work of sorting out the problem. Hopefuly it is not too late by then, but it has caused a load of waste activity to ripple through the organisation.
One day someone will come up with the bright idea of in the first instance, getting the caller to talk directly to the person who can help them resolve the problem, and that same manager who set up the big building full of call handlers will find that the cost of doing this is considerably less than the old way. And, as a by product, the service is markedly improved.
It is what happens to all such contact centres if they are analysed in the right way, but it takes so many of us to make the expensive mistake before we learn that lesson. By that time, a new manager has taken the reigns, and they have a great idea to solve the cost of different localities taking their own calls... The wheel goes round again.
Take a systems thinking approach to this problem, and the right solution will be clear.
Scottish policing article from Ian Wiggett

So, you have decided to log demand into the police. Make sure you look at all the demands coming in, they come in on the phone, by email, and into the enquiry counters. And what about when officers are on the beat, and from the phone at enquiry counters, don't forget those...
Then a table is made up of demand. And if youre thinking a little further, you decide to focus using an outside-in perspective, to see what REAL demands are coming in. So split the demand into value and failure demands. Take a systems thinking view of demand.
The demand coming into the police are far more tricky to analyse than transactional based system. Why? well, because these demands are:
1. They are varied. Some demand is a simple questions, some are for requests for police service, and others are just plain calls for help. If you try and combine them together, on a spreadsheet, then you may be working with data that is just too summarised to make any real decisions on. A demand for a shotgun licence, to a call to attend a historic burglary, to a call for a domestic issue, to a call asking about help on a civil matter. Some of those demands will take a great deal of time to answer, and what matters to the caller and the subsequent response is vastly different.
2. In a simpler system, like a bank, a demand is a call for service, and the service delivery follows that demand. With the police a demand may be followed up by subsequent demands, that are of value. They represent communciation that is part of the flow of work. Maybe in these cases it is better to view these demands as in process demands.
If you treat the demands above as the same for computational and analysis purposes, you will aggregate apples and pairs as being the same fruit. And how useful will the information be? Maybe a better way is to look at the police system from an outside in perspective, and group demands into:
a. Transactional demands - that starts as a demand from the public, and the police provide a service or answer, and then it is complete. These transactional demands can then be further categorised.
b. Help me demands - where a member of the public needs help and support. These cases are sometimes complex, sometimes not directly do with the police, and their resolution may be long term.
c. Different types of demands follow different flows of work. If they do, then these demands are different and be wary of aggregating them into statistics.
So, whats the best thing to do with demands into the police? Be very wary of categorising them to any standard apart from that from the outside in perspective, and use what matters as a guide. Then you will create groups of demands that will truly be useful to operations to analyse how to deal with them.
Real Lean, when combined with systems thinking, gives a view of your organisation that is often difficult to view, in todays pressured and prioritised environment. Using it will help you to see why certain issues remain resistant to change, regardless of how many consultants, or how much money is thrown at it.
A link to Joan Donnelly article on Demand, from Policing Insight here
Then a table is made up of demand. And if youre thinking a little further, you decide to focus using an outside-in perspective, to see what REAL demands are coming in. So split the demand into value and failure demands. Take a systems thinking view of demand.
The demand coming into the police are far more tricky to analyse than transactional based system. Why? well, because these demands are:
1. They are varied. Some demand is a simple questions, some are for requests for police service, and others are just plain calls for help. If you try and combine them together, on a spreadsheet, then you may be working with data that is just too summarised to make any real decisions on. A demand for a shotgun licence, to a call to attend a historic burglary, to a call for a domestic issue, to a call asking about help on a civil matter. Some of those demands will take a great deal of time to answer, and what matters to the caller and the subsequent response is vastly different.
2. In a simpler system, like a bank, a demand is a call for service, and the service delivery follows that demand. With the police a demand may be followed up by subsequent demands, that are of value. They represent communciation that is part of the flow of work. Maybe in these cases it is better to view these demands as in process demands.
If you treat the demands above as the same for computational and analysis purposes, you will aggregate apples and pairs as being the same fruit. And how useful will the information be? Maybe a better way is to look at the police system from an outside in perspective, and group demands into:
a. Transactional demands - that starts as a demand from the public, and the police provide a service or answer, and then it is complete. These transactional demands can then be further categorised.
b. Help me demands - where a member of the public needs help and support. These cases are sometimes complex, sometimes not directly do with the police, and their resolution may be long term.
c. Different types of demands follow different flows of work. If they do, then these demands are different and be wary of aggregating them into statistics.
So, whats the best thing to do with demands into the police? Be very wary of categorising them to any standard apart from that from the outside in perspective, and use what matters as a guide. Then you will create groups of demands that will truly be useful to operations to analyse how to deal with them.
Real Lean, when combined with systems thinking, gives a view of your organisation that is often difficult to view, in todays pressured and prioritised environment. Using it will help you to see why certain issues remain resistant to change, regardless of how many consultants, or how much money is thrown at it.
A link to Joan Donnelly article on Demand, from Policing Insight here

I was reading an article writen by John Bird, he of the Big Issue. In it he talked about the benefits system, the TV programme Benefits Street, and the ability to 'benefit' people. He has hit on a point that has been demonstrated in the last few years, by a few people.
In Stoke on Trent, they have experimented with trying a different way to deal with people who are struggling with something in their lives. This struggle is affecting them in ways like an inability to pay rent, running out of money, needing to get on the waiting list, etc.
What the team did was to take some people in need, and ask them what problems did they have that they needed help with? And whatever they said, the team would go about helping the person to fix that problem. It was that easy.
Chief executives from a range of public sector partners has agreed that the team has the ability to pull on any service they needed to to get the competence to fix the problem. In addition, the action they took and money they needed to put towards helping that person, was available to be spent.
The team took cases, and the first step was to understand the problems the person was facing, and the nature of their problems in the context of their lives. The next step was to then do only what is necessary to help the person resolve their problems.
What was found, was that the people they took, had a range of interdependent problems, that often took time to properly understand. Often, people were wary of this approach from an organsiation they did not trust.
Then, the team found that the problems that were presented with, were not usually solved by taking the standard approach that that service would normally take. For instance, if someone wanted to move, the first thing to do is to understand the reason for the move. It was discivered that most people who wanted to move, actually had problems that could be resolved, that meant that they then did not need to move.
The outcome is that the people with needs to be resolved, actually had their problems fixed, or had ways that they could continue to resolve the issues on their own. The majority of people that went through this system accepted the help, and the outcomes were positive in every situation.
It is difficult, in a short time to view actual financial benefits. However, the team calculated that for seven cases, the difference in the cost of the work done was £104,000 less in the new way. Even understanding that this figure is an estimate, the amount is staggering.
Another outcome, and one that is just as important, is the impact it had on the people. The intervention on each person was aimed at re-balancing them so that they could then continue to live their lives to develop into becoming independent of the welfare system.
The reason I wrote this example now is that John Birds article said that the benefits system should 'benefit' people. Benefit people in need, to help them to fix problems and improve their lives. The work that has been trialled, using a systems thinking approach, shows that this is not only possible, but that it actually reduces the cost to the whole system. The cost further reduces over time, as people are less dependent and more in control of their lives.
In Stoke on Trent, they have experimented with trying a different way to deal with people who are struggling with something in their lives. This struggle is affecting them in ways like an inability to pay rent, running out of money, needing to get on the waiting list, etc.
What the team did was to take some people in need, and ask them what problems did they have that they needed help with? And whatever they said, the team would go about helping the person to fix that problem. It was that easy.
Chief executives from a range of public sector partners has agreed that the team has the ability to pull on any service they needed to to get the competence to fix the problem. In addition, the action they took and money they needed to put towards helping that person, was available to be spent.
The team took cases, and the first step was to understand the problems the person was facing, and the nature of their problems in the context of their lives. The next step was to then do only what is necessary to help the person resolve their problems.
What was found, was that the people they took, had a range of interdependent problems, that often took time to properly understand. Often, people were wary of this approach from an organsiation they did not trust.
Then, the team found that the problems that were presented with, were not usually solved by taking the standard approach that that service would normally take. For instance, if someone wanted to move, the first thing to do is to understand the reason for the move. It was discivered that most people who wanted to move, actually had problems that could be resolved, that meant that they then did not need to move.
The outcome is that the people with needs to be resolved, actually had their problems fixed, or had ways that they could continue to resolve the issues on their own. The majority of people that went through this system accepted the help, and the outcomes were positive in every situation.
It is difficult, in a short time to view actual financial benefits. However, the team calculated that for seven cases, the difference in the cost of the work done was £104,000 less in the new way. Even understanding that this figure is an estimate, the amount is staggering.
Another outcome, and one that is just as important, is the impact it had on the people. The intervention on each person was aimed at re-balancing them so that they could then continue to live their lives to develop into becoming independent of the welfare system.
The reason I wrote this example now is that John Birds article said that the benefits system should 'benefit' people. Benefit people in need, to help them to fix problems and improve their lives. The work that has been trialled, using a systems thinking approach, shows that this is not only possible, but that it actually reduces the cost to the whole system. The cost further reduces over time, as people are less dependent and more in control of their lives.
Commissioning and outsourcing has failed in the public sector, and we need to learn the lessons for next time someone in government thinks they have a good idea
We probably have to thank Margaret Thatcher for creating the space in the public sector to embrace outsourcing and commissioning. The idea was to inject private sector thinking in to a local authority. A very good idea... Local authorities are in sore need of being able to manage and view their organsiations differently, especially when there is no real impetus for change.
Did it work? Was it the right thing to do? Well, introducing elements of the private sector is fine as long as they are the right elements, but what have we been left with? Competition! Thats the method that is used in commissioning and outsourcing to drive down costs and improve service. Thats all very well if we can draw parallels between the private sector customer connsumer ethos. But a council does not providing a consumer service, they do something very different.
So the impact of outsourcing and commissioning in a local authority has been to reduce costs for those services from an accounting perspective. However, the impact of outsourcing in reality is being locked to a fixed agreement: unable to change, being charged for additional work, unwillingness to work across other services, and potentially costs not being reduced in the long term. The woes of a service that has been outsourced are legendary.
Universal Credit has outsourcing at its heart, and despite all attempts to 'fix it' the root cause of the flawed design is at its heart.
Today, councils all over the UK have realised that this appropach has largely failed. And they are rapidly taking most of those same services back in-house.
Did it work? Was it the right thing to do? Well, introducing elements of the private sector is fine as long as they are the right elements, but what have we been left with? Competition! Thats the method that is used in commissioning and outsourcing to drive down costs and improve service. Thats all very well if we can draw parallels between the private sector customer connsumer ethos. But a council does not providing a consumer service, they do something very different.
So the impact of outsourcing and commissioning in a local authority has been to reduce costs for those services from an accounting perspective. However, the impact of outsourcing in reality is being locked to a fixed agreement: unable to change, being charged for additional work, unwillingness to work across other services, and potentially costs not being reduced in the long term. The woes of a service that has been outsourced are legendary.
Universal Credit has outsourcing at its heart, and despite all attempts to 'fix it' the root cause of the flawed design is at its heart.
Today, councils all over the UK have realised that this appropach has largely failed. And they are rapidly taking most of those same services back in-house.
What is the problem?
Looking at outsourcing systemically, there are two main aspects of this approach that point to inappropriate design.
1. Outcourcing works by designing services functionally. This also meanas that they have to be defined by standard flows and procedures. Many public sector demands require flexibility, continuity of knowledge, and they change over time. Thiese factors cnnot be served by this standardisation.
2. Dealing with complexity using standard transactionally designed services simply will not work. transactions are defined by tame and linear defined workflows. Complexity is defined by dealing with demands as they present themselves according to their context. This confusion in design will drive up cost and create a very poor outcome.
In both cases an understanding of systems thinking and complexity will point the way to a design that fits people centred services.
1. Outcourcing works by designing services functionally. This also meanas that they have to be defined by standard flows and procedures. Many public sector demands require flexibility, continuity of knowledge, and they change over time. Thiese factors cnnot be served by this standardisation.
2. Dealing with complexity using standard transactionally designed services simply will not work. transactions are defined by tame and linear defined workflows. Complexity is defined by dealing with demands as they present themselves according to their context. This confusion in design will drive up cost and create a very poor outcome.
In both cases an understanding of systems thinking and complexity will point the way to a design that fits people centred services.
Can it work?
Commissioning and outsourcing can work if you can get agreement based around a common systemic purpose. And the agreement is based on true cost (open book). If not, then you get the problems with commissioning that is destroying the NHS.
As an example, Fareham council is redesigning its services using a systems thinking approach. Their managers have alreasy redesigned their own services, and are continuing to refine their effectiveness. Its only by transformation that any organisation can achieve effective reduction in cost. They have also outsourced where appropriate, but in the main, they have decided to get the right sort of management of their services and deal with most things in-house.
As an example, Fareham council is redesigning its services using a systems thinking approach. Their managers have alreasy redesigned their own services, and are continuing to refine their effectiveness. Its only by transformation that any organisation can achieve effective reduction in cost. They have also outsourced where appropriate, but in the main, they have decided to get the right sort of management of their services and deal with most things in-house.