Archive | Systems Thinking RSS for this section

How can I push the software development team to go faster?

A common challenge I’ve heard from Development Managers or Product Owners is “how do I push my software development team to go faster?” Here are ideas on how to approach this topic and have more productive conversations.

Push

Understand your own mind

Start by clarifying your own mind, particularly your intention and motive for trying to get the team to go faster. If there increasing external pressures on the project, or it’s becoming clear that it wont be possible to get everything you hoped for by the due date then these are worth clarifying and sharing with the team.

Take the time to understand where you’re coming from and why.

This step may seem obvious, but it’s worth slowing this down and even talking it through with a mentor or trusted peer and asking them to play devils advocate and try to see things from the team’s perspective.  It’s much better to get clear on your own intentions and motives than to mop up from an argument later.

Focussing on “fast” may have unintended impacts on quality

As the old saying goes, “be careful what you wish for” because you may get it, but at the expense of other goals.  Sometimes to go faster you may need to use indirect or oblique strategies, such as removing the causes of bad quality or delays.

Seek to understand the situation by looking for evidence

If you think that the team is going slower than it could be, then get clear on the evidence you’ve seen or heard that leads you to this view. If you tell a team “I think you can push a bit harder and work faster” but can’t use specific examples that they recognise and understand then it’s likely they’ll feel unjustly accused. See my post on handling a team member who talks ‘too much‘ for an example of using directly observable data.

If you can’t be specific about why you think the team could be going faster, then be open and say so – “this is just a hunch” – You could ask the team to help look for evidence, by asking “If you were performing under or over-capacity, what would we look for as evidence?”

Talk to the team, sharing interests and concerns

Talk to the team about why you want to help them get more done. Share your intent for bringing it up.  Start by sharing what you’ve seen or heard. Ask them what their view is of the evidence you’ve got? Do they see it the same or different?  If they see it differently then get curious and ask them what they see that leads them to their view.

Sometimes the conversation can get bogged down under an escalating game of “no, your approach is bad for this reason, we should do my approach”. One way to avoid this conversational log-jam is to focus on the interests behind the positions, or more simply, ask them what they like about the solution they’ve proposed.

I’ve found the best way of encouraging more productive conversations is to learn and model these more effective approaches yourself.

Jointly design ways to tests disagreements and move forward

If there’s a strong disagreement between you and team about the level of productivity, then focus on jointly designing ways that you could move forward. Think about what data would persuade you from your point of view and ask the same of the team.  Use work that is about to begin and come up with a way of collecting data that would make future conversations clearer.

This is a topic I may come back to in future and look at it from the team’s perspective.

Image Credit: gentlemanhog, on Flickr

Benjamin Mitchell's Twitter ProfileHi, I’m Benjamin. I hope that you enjoyed the post. I’m a consultant and coach who helps IT teams and their managers create more effective business results. You can find out more about me and my services. Contact me for a conversation about your situation and how I could help.

Removing the bubbles: solving bottlenecks in software product development

A challenge with software product development is visualising the work so that you can spot where there are delays in the process of converting ideas from “concept to cash”. This post shows how a cumulative flow diagram helped identify a pattern of queues over time. Removing these queues had many benefits such as fewer errors, increased team communication and improved team capacity.

Make the work visible
The first task is making the work visible. In knowledge work, such as software development, it is difficult to see the work being done, which is why a visualisation approach such as kanban can be so useful. Here’s a view of a kanban board from an earlier client team:

Kanban Board

The kanban board is useful for a “moment in time” view, but it’s not possible to easily see patterns that might develop over time. Looking at the kanban board on a particular day doesn’t make it easy to answer questions like these:

To find these answers and look more clearly for patterns over time we built a cumulative flow diagram (CFD, also called a ‘finger chart’) by counting the number of post-it notes in each stage (column) in the team’s process after each daily stand-up. Unlike my earlier post on using three forks and a hand-drawn chart to help a team improve in this case we used an Excel spread sheet.

Visualise the work over time to better understand queues (‘bubbles’)
The cumulative flow diagram for this team helped make visible that there were consistent queues of work in the functional testing and acceptance testing processes over time. These queues are visible as “bubbles” that develop in the cumulative flow diagram.  See the highlighted in orange and red stages below (click the image for a larger version).

Cumulative Flow Diagram

Do the detective work necessary to understand what causes the queues (‘bubbles’)
Around two-thirds of the way through the above chart (which covered about 36 weeks) we decided to focus on studying what was causing the queues to develop in functional and acceptance testing.

The functional testing involved someone other than the person who developed the functionality (user story) validating that it worked functionally (there were no obvious errors). Once functional testing was complete then the acceptance testing stage was performed by a business analyst or the product manager.

The team were releasing to production every second Wednesday. On the middle Wednesday the person who did the functional testing switched to doing the integration testing (ensuring the features which were created as a package to go to production worked individually and combined, as well as running a set of manual regression test scripts to make sure that the new functionality hadn’t had any impact on the rest of the website). During the week spent on Integration testing, no functional testing was done, which we believed was the cause of the queues or orange bubbles on the chart.

Creating a new policy to reduce the queues (‘bubbles’)
We sat down with the person who performed the Functional and Integration Testing and mapped out the schedule of their work across the fortnight between releases (see the hand-drawn diagram we came up with below).

The fortnightly plan of testing the project

We also mapped out a new “policy” that described what the person doing testing did for for the week spent integration testing:

While performing the Integration Testing in the week before the release, if there are any work items in the Functional Testing column, spend up to an hour each day doing them.

We experimented with the new policy for the last third of the cumulative flow chart. The cumulative flow diagram showed that the queue (bubble) in the Functional Testing (orange) step virtually disappeared, as did the queue in the Acceptance Testing (red) stage. The CFD not only highlighted the initial problem, but it also validated the experimental change we made in policy resulted in an improvement (it allowed us to answer the critical question – “did the change we made to our process result in an improvement?”)

It’s the system!
This example demonstrates how changing the way the work is structured can produce improvements without having to change the work that team members were doing. This example shows that the queues caused by the way the work was structured (e.g. the system we had designed) and not the work of the team members. It speaks to Deming’s ‘provocation’ that “95% of the variation [in how long the work takes] is due to the system and not the individuals”.

Benefits
There were many benefits to the changes that we made above:

  • Removing the queue in functional testing meant that if a problem was found then the developer got faster feedback. Getting feedback faster reduced the time it took a developer to “get their head back into the issue” and fix the problems. It also improved the communication between members of the team – the developers were more likely to speak to the person who did test at stand-up about the work that was coming because they knew it would be tested quickly, rather than potentially sitting in a queue waiting for a week.
  • By reducing the bottleneck in Functional Testing also reduced the same bottleneck in Acceptance Testing.
  • The reduced “thrashing” from having issues discovered close to the release date meant the team’s capacity to do work increased.
  • As there were fewer queues it reduced the pressure on team members, helping them feel less rushed which improved the quality of life for the team, reduced “rushing” leading to better quality and team morale.

Benjamin Mitchell's Twitter ProfileHi, I’m Benjamin. I hope that you enjoyed the post. I’m a consultant and coach who helps IT teams and their managers create more effective business results. You can find out more about me and my services. Contact me for a conversation about your situation and how I could help.

Steve Allder: Systems Thinking in Health Services

Seddon introduces Steve by saying he’s done Systems Thinking without Vanguard. The only difference between having Vanguard consultants, versus doing itself, is that it may take longer and you may make more mistakes, but Vanguard’s purpose is to change management thinking, so they are happy for others to use their method.

Steve Allder is a consultant neurologist at Pymouth NHS hospital Trusts.  They had the worst stroke mortality in their region.  Strokes showed very consistent demand, but the length of stay in the stroke unit was incredibly variable. They were spending £6k on each patient, but being funded only £4k.  There was lots of debates about how to solve the problem. The government implemented targets, but no-one in the discussions at the local trust had any data, it was only folklore and opinion.  The two CEOs knew they didn’t have anything to spend on this, so Steve promised to get something without needing to spend.

If you come in with a stroke, you now go (within 2 hours on average) to the Stroke unit straight away. 100% of stroke patients go to the unit (previously 60%). The length of stay has dropped from 16 to 6 days. They are the only unit in the country to get near the government target of 90% (currently up to 80%).  They now ‘save’ £1K a stroke patient, with improved care. 

What has this got to do with Systems Thinking?

Steve was going to get a t-shirt saying “Peter Senge Change My Life” due to the pain of trying to create change. He liked Senge’s limiting conditions work.  You need to balance working on improvements with working on the limiting conditions, which was helpful for Steve.  He then read Seddon’s “Freedom from Command and Control” and got ideas like “true knowledge can easily be missed by the prevailing group, but the prevailing book has the power”.

For Steve, the words were “Purpose, Value, Demand, End to End and Capability”. It’s best to go in with an open mind and go back to first principles.  The value of Systems Thinking is that once you’ve learnt something it’s not possible to ‘unlearn’ – e.g. a point like ‘get knowledge’

The key to Steve’s intervention was an understanding of the six different groups within stroke patients (took 4 years of iterating to find this). Most patients were frail before they had a stroke, and had a huge stroke, which averaged a 50 day stay. The patients and the relatives just wanted to keep them comfortable, but we kept putting feeders into them.  Now we’ve recognised the patient group and talk about what might happen and they say “just keep them comfortable [rather than doing everything medically possible]”.  That group has radically improved.

If you were well before a big stroke, then you have to go to rehab, but the rehab unit would say “they are not well enough”, but for frail elderly patients they may not be up to rehab, they may just need time with nursing care.  Now they use that end-to-end lens, it’s liberated how they manage patients.  This has lead to all of the benefits they’ve got.

It wont work without a cast iron mandate

It is difficult to explain Systems Thinking to others. Steve has had this with most of the NHS. Steve talks about Flatland from “The Happiness Hypothesis” about a sphere visiting ‘flatland’ and everyone sees the sphere as a circle, getting bigger and smaller, but the two-dimensional square can’t understand the third dimension (“thickness as well as height, you say?”). The sphere yanks the square out of flatland into the third dimension and feels sickened and unnerved. When the square returns to flatland he can’t ‘preach the gospel’ to the other two-dimensional shapes.

Everyone in health agrees high quality and low cost, but don’t know how to get there. Steve says you need to work on the thinking.

What could this mean for the NHS?

As well as meeting the financial challenge it will help give patients what they need and allow employees to connect to their internal motivation and serve the wider society. You don’t know when you’ll need the NHS, but when you do, you’ll need it fast.

Questions and Answers

Why did it take so long to find out the different types of customers?

Because I wasn’t expecting it, it took me a while to understand what the data was telling me because I wasn’t expecting to see it.  The first thing I did was to do the capability chart without trying to guess what the answer would be.  Now, in health, frailty and multiple issues are current topics, so this might make it easier next time.

Seddon: The purpose of time-series data is to ask better question.  You might have to look at the data for a while, then get an inspiration and run more data.

The NHS has an issues of the revolving door with substance abuse. We’d like to engage with people earlier and get at the social issues at the cause of substance abuse. Do you have an idea about how to get through the medical arguments that doctors don’t want 3rd parties on the wards. Any advice?

We need a psycho-social model of health combined with a Systems Thinking approach.  Try and find the right advocate – a doctor outside the Trust with links inside and empower them to find someone credible in the NHS who has influence. It’s difficult to get traction.

Is there a way of extending what you’ve done to the rest of the hospital without getting managers to agree to it?

65% of beds are used by people who are stuck. The clinicians are unable to fix that. The managers, who work in the PCT / Local Authority, need to understand this, and they behave very badly.

Seddon: There’s a designed-in problem between clinicians and managers [not sure I got this right].  A bed manager is an absurd idea for a Systems Thinker.

Can you use Systems Thinking to help the community earlier in the health pathway?

GPs are paid to get blood pressure. Where we are, we have great GPs and blood pressure treatment is great.  Treatment of blood thining was not so good, but the demand data said there are only 4 patients per practice. Instead of an ‘education program’ they now ring the patients.  Now I look for the data, quantify the demand, and there’s somebody in the system that should already be doing it, and just need a little nudge.

Seddon: Isn’t it amazing we have a health service that doesn’t understand demand.

Steve: my aha moment was when the waiting time to see me or have a test was two years.  I was thinking ‘what value can I be adding?’. At that time, I thought ‘there’s not enough money and demand is increasing’ but that wasn’t correct. Demand is predictable and stable, the problem is the way we’ve designed the work.

How do I persuade my clinical colleagues that Systems Thinking will help them?

I am in management, but use the same approach to management that I used as a clinician. I have a framework, I gather data.  The problem is not the clinicians, the problem is getting their management to free up some time and support so that they might change things. Clinicians say they want to change, they just want someone to facilitate it. Find like-minded colleagues and look for easy starting points.

Seddon: Vanguard have found clinicians lap it up because they like to ‘get knowledge’.  The problem is that managers and the Dept of Health and they have been created in the last 20 years, and they believe they are doing “God’s Work”.  You need to get them out to study the system, and their thinking changes.

Why do clinicians change when they become managers?

I don’t think they do. McKinsey have found a correlation between improved productivity and percentage of clinicians in management roles.  If you show them the data they will respond to you. My experience hasn’t been that clinical managers change when they become managers.  There is a problem when managers don’t have a framework.

People who understand Systems Thinking feel liberated, so they often sound like they are talking about the spiritual and the divine.

Seddon: A clinician CEO ‘got it’, but the appointed non-clinical staff

Systems Thinking in Local Authorities

[Post-lunch dip was strong, so this session’s notes are not as comprehensive]

Phil Badley, Stockport

Interesting to hear Phil talk about his own realisation that his area, HR, was full of the same errors that he’d seen in other areas of the business.  I’d like to find out more about what it was that helped him go through this experience.  Phil Badly spoke about leadership buy-in.  Seddon says if you want to make organisational change, you need CEO or Local Authority buy-in, otherwise your chances are limited.

Denise Lyon, East Devon Council

The experience of going through Check was like an “honesty mirror” because the news we discovered was horrible.  They spent five out of six weeks of Check was spent arguing who the customer was, not what service they were getting.  They were horrified by how bad the service really was (141 days for some activities). It was so shocking because we had no measures in place that would have helped us see/understand this.  Our national indicators showed they were not meeting some measures, but none of them showed the scale of the problem.  Understanding value or failure (called “preventable demand” because staff didn’t like it) and one-stop capability and end to end times allowed them to see and understand their service levels. Their previous measures were always applied after the event.

The question they keep coming back to is, “who is accountable for this service? Which manager in this hierarchy of managers is responsible? Who’s feet do you hold to the fire?” Most managers thought “It’s not me; I’m strategic!” whilst the next level said “It’s not me, I’m strategic too! I’m too busy to deal with this!” while the manager at the bottom was looking at the top saying “You higher managers are paid a lot more than me, so it must be you!”

They don’t call them “interventions” (too much like Audit commission) so they call them reviews, but it’s stopped at management.  It’s only two years later that they are starting to do “something radical”(?) with the “management piece”.

The Vanguard consultant is described as a “class 1 drug” and a “mind bending hallucinogen” and a “guru” who was central to making fundamental changes to our thinking.

John van de Laarschot, Stoke City Council

John spoke about the idea of ‘red’ hats and ‘green’ hats (which I think refers to the idea, if there was a fire and everyone left the building, who would you let back in first, because they were central to doing business, and who would come in last) and discovered that 50% of their staff don’t contact the customers!

Interesting capability chart that showed after the initial intervention, performance trended worse for a period, showing that thinking hadn’t fully changed (people reverted to older behaviour).  John spoke about the need to “not walk away” from the intervention.

Example of Surface Water Management. A preventative maintenance program was set up to send a truck around on a calendar schedule, but the city is a flood risk so when it rains there are huge problems. But this shouldn’t happen because there’s a preventative program.  However, the frequency of maintenance didn’t match the fact that the drains at the bottom of the hill needed more cleaning than those at the top!  They overlaid the geography of the city onto the drains and re-drew the maintenance program.  They even used Google Earth to help with the mapping, with a “young person” (I love this phrase!).

Challenges are the scale and scope of the potential changes.  It’s hard to create the space to explore new ways of doing things. You can’t do this on a shoe-string (if you don’t have the capacity it will probably go slower).  There are also big political implications (often opposition groups want to ‘put it in a coffin’).  Systems Thinking creates a ‘different type of critter (employee)’ so there are issues of demarcation so having the Union on board at the start is important. 

Question and Answer Session

Q: Could John say more about ‘top level reporting’ with ‘systems thinking slipped in underneath’

John: Local Authorities are familiar with classical accounting and McKinsey / PwC. The type of methodology we want, to get change going, requires clear buy-in. The first attempts I had at selling the organisation on Systems Thinking was “we think it’s you and your mates”, so we needed to be ‘creative’. We’ve had Vanguard and PwC in the same room; and it’s like oil and water.  Out of the work that we’ve done, we’ve managed to keep them away from our customer-oriented interventions.  We were able to show it in ways that Command and Control types can understand. [So they showed reports and model to Command and Control types while running a separate set of ‘books’ showing their Systems Thinking view of the world]

Seddon: When you get to the evidence, it speaks for itself, but then you have a problem that people want it for the wrong reason.  I want it because it works, not because it’s about thinking. Buy-in is the wrong word, ‘understanding’ is the thing.  The Vanguard Network is for middle-managers to do the Vanguard Method but not telling the boss, which we encourage them to do.

Denise: Support was essential for the funding, support, opportunity to view other places.  If you can do it yourself, in your part of the organisation, then this might be a good start – better than no start, I think.

Q: If you hadn’t done Systems Thinking, where would you be now?

Denise: We were in the bottom quartile in national rankings. As time has moved on, and the financial crisis has hit, we have been in a good position to understand how we can sensibly take out from management and services. I dread to think about Local Authorities that are doing 10 – 20% cuts across all services, which I think is a poor way to manage. We feel in a strong position in the troubled times we’re in.

Q: Where was your ‘moment of truth?’ where you said ‘I will never do it the other way?’

Phil: Reading Seddon’s “Systems Thinking in the Public Sector”. I read it on holiday and realised that I’d been accountable for change in the past, and now understood ‘why’ it didn’t stick.

Seddon: The number of people who tell me “I wished I’d never met you …” (joke)

Rob Brown: Systems Thinking in a Complex Organisation

Rob Brown from Aviva is up next.  They started in 2008 with Barry Wrighton from Vanguard (also involved with BNP Paribas Fortis).  He’s currently the Lead for Systems Thinking but looks forward to the day when his role is obsolete.

Some of Rob’s learning are that Senior Management engagement is crucial. They have gone at the pace of the leader’s understanding.  In the Policyholder contact area they have no targets but have gone from 50 – 92% customer satisfaction in 6 months with a ‘clean audit’ with no issues.  The pace has been driven by the correct leadership engagements at all levels.  It took them several years for general insurance to start with their journey, but it is down to people decided when they want to start.  They decided to ‘see what would happen if they tried’.

Phrases from Senior Leaders to watch out for when introducing Systems Thinking

If he had his time again, the killer phrases he would look out for are:

  • When a leader says “I’ll delegate that to …” because they will be a blocker to redesign.  Where it has happened it didn’t work.
  • “What targets do we use?”. Senior managers, not in the work, want to set a ‘stretch target’ to get ‘better Systems Thinking’
  • “I get it!” when a leader says this, it usually is followed up with a question that shows they don’t. You have to get past the ego to get onto the work.  We have worked without/despite leaders but it has been hard.  They need to hold a mirror up to say “we need to do this in your area” in order to have dramatic further progress.
  • “Why can’t you go faster?”. Even though other projects have produced no benefits but were delivered to date/time targets, people still find Systems Thinking hard to understand.

Budgets, Plans, Risks & Regulation, Audit

It was important for them to work with the audit team so that they understood the new process.  Legal, Compliance and Risk said they felt they were labelled “Level 3″ waste (incorrectly). It’s been much better to work together with them so that they develop an understanding.

Observations from Check

There were 500+ numbers customers could use to ring in, with 48 Integrated Voice Response systems (IVR) with call centres for different product silos.  16% of all calls were transferred (which would happen given the IVRs). Customers were on hold for a quarter of the call (a single loop fix was to ‘choose better music for customers on hold’!). 15% were passed-back, 42% passed on.  Then there was the split as the call went into a back office system. Typically customers called in 3 or 4 times for a single piece of work! Yet, all of this was happening while we were ‘green’ on budgets and targets. But 50% of the time we were not giving customers what they want. By looking at the work differently, after re-design, they were able to turn off off-shoring and achieve 92% value demand.

Summary

There has been a move from intervention support to a focus on leadership and embedding behaviours.  To fully embed Systems Thinking they need much more work at all levels.

Question and Answers (with Benny Devos)

Benny on Emotional Intelligence and Systems Thinking:

People have to be open. The management used to ask people to take their brains out of their heads as they arrived at work, only to put them in when they left the building. The manager needs to understand what the customer wants as well as his team. Therefore, you need empathy. Also, the manager has to change personally.  The leader needs to help the team become leaders themselves. You need EI to detect how other people are thinking.

People change is often thought of as being a HR function. How has HR been?

Rob: We’ve learnt some lesson. When changing roles and remuneration, HR didn’t get it. What we should have done was take them through the work much more before that point. We are part of a global company and I can’t switch off the remuneration.  What we have done is given Systems Thinkers to remunerate as they see fit.  We have a new HR Director and understands that HR needs to understand how they can help if Systems Thinking is going to be extended. HR knows they don’t need to ‘do culture’.  We had employee forums who felt threatened, so we took them in and allowed them to see and understand themselves.

Benny: HR people were in the intervention from the beginning.  What we saw was that if you needed a decision you had to re-explain what it is all about. If you put enough energy in then they accept it and it changes. But this is counter-productive and wasteful because the solution takes a long time. In terms of the workers council, in Belgium, you had to go to a council every time. They were skeptical, given the McKinsey experience, so we explained and invited them to the work floor. We invited them and involved them and they understood.

Seddon: A lot of HR is dealing with symptoms of traditional Command and Control design. When you change the system, many HR symptoms go away.

Would Systems Thinking have prevented Sub-prime in the Banking arena?

Rob: If you understand the controls, and they are part of the work, and specialties help design it, it is much better control than the ‘remote sign-offs’ that most businesses used.  Sign-offs are fine until something happens, but with Systems Thinking the right people are involved at the right time, so it’s a stronger sense of control.

Benny: Don’t repair – put right the first time.  Top managers don’t have any understanding of what they are signing off – it doesn’t make sense.

Seddon: The regulators played a part. Regulation is a catch-up. They assume it applies to all products. They should make it a preventative thing. You shouldn’t be able to launch a financial product without showing what it would do. Politicians also thought that finance would drive growth. Some economists think that financial servers should help the economy, not be an economy in its own right.

“We’ve also done it this way, it’s how it works … it’s how it’s regulated”. Is there any one thing you’ve done that helps managers avoid this? where do you start in terms of getting people to think in a different way:

Rob: Get the right people to look at what’s happening in the work differently. You can’t have a debate about ‘what’s the better method’ – focus on getting people to see what’s going wrong and allow that to drive what should be done differently. Leaders should look at their world differently. Don’t do it at tables in offices.

Seddon: It’s an intervention problem. Man is not rational. It is not I explain, you understand. It just creates conflict with two mindsets using different language. If you put them in a normative experience then together they develop, building a common understanding, and that helps the change.

Benny: It’s a common understanding, and it’s not the managers that are doing the redesign, it is the workers. They do trial and error and demonstrated that it’s not normative. The managers were focussed on the measures, not how the work is done. We focussed on ‘positive’ people and worked with them. We gave managers an ‘Informed Choice’ some managers wanted to join early.  They were only rolled in if they wanted to.  Those who decided not to, went to different areas.

Seddon: Roll-in is a deliberate phrase we use instead of ‘roll-out’. Now that we have understanding, how do we ‘roll people in’. We need people to see the relationship between assumptions and policies, which requires normative experience.  You might think this will take longer – but try doing the wrong thing, it will never happen!

Another question on Emotional Intelligence. In the examples there were less workers, was this a threat to the rest of the workforce?

Rob: We had a cost-reduction promise hanging over us, which is tricky. We faced up to this fact and had discussion about the fact it would happen, but we would do it from a ‘where’s the value’. It was tough. We told the frontline that they were sacrosanct because they understood the demand.  People work out that you may not need as many people, but there are lots of other places they could go in the organisation to add value.

Benny: The biggest problem was getting people to believe that we weren’t threatening jobs (there was no budget or cuts over our heads). People didn’t believe me; it took time, energy, talk and waste from my point of view to convince them. It’s a normative experience; they find out themselves.

Seddon: Systems Thinking in the private sector is about driving growth.  We provide a framework, so if you have to take people out, it helps make sensible decisions about where to take people out.  We tend to always find too many people in the “management factory” (which Seddon admitted was pejorative)?

Owen Buckwell: Systems Thinking in Housing Services

Owen Buckwell is describing the award-winning work as Head of Housing at Portsmouth Council.  Here are a selection of key points

Things they used to pay attention to now take care of themselves.  For example there is no more training events for morale. We don’t manage sickness, but sickness leave has gone down. 65% of all sickness is with 20% of the people (grounds maintenance) and the cause of their issues was back pain. So we’ve given them training on how to lift and sicknesses have gone down! Cleaners were eating without washing their hands and getting stomach issues, so now we’ve given them hand gels.  Awesome example of studying the system and going to find root causes, rather than working on the symptoms!

They no longer spend with Vanguard, they lead the change themselves now.

A control chart(!) shows that formal complaints about housing repairs have fallen (80% reduction).

Ian Gilson, from Comserve, a contractor to Porstmouth Council is on the stage.  He speaks about the Vanguard intervention in October 2008.  Multi-trade Supplies was invented after this intervention.  Owen used “brute force” on Comserve to force the contractors to look at their service from outside-in.  The measures that they used showed they were doing well.  Owen took them to the tenants and walk through the jobs to identify the issues, which ‘opened their eyes’ and ‘made them curious’ about what they saw. Ian mentions that they realised they had ‘management filters’ which prevented them from seeing the problems of the work.

In ‘Check’ they realised they had no effective measures of the work, or to understand the purpose (above ‘make money and provide a decent service’). They found a lot of waste – replacing a wooden front door took four visits! They used to go at times that were not convenient to the tenants and surprise, the tenants weren’t there.  The people wanted to do a good job but the system wasn’t letting them.  Check is very difficult for a leader of a business to go through, since the leaders have created the systems that cause the problem (not enough stock in the van because they weren’t trusted to have the stock).  They had to go through an un-learning about the fact that what you were doing that you thought was effective is not.

In ‘Redesign’ they talked about the ‘art of the possible’ and started with a ‘blank slate’. They worked with John Little from Vanguard.  They started to run experiments and identified the purpose (‘Do the right work at the right time’). The tenants want a first-time fix, in one visit.  The right time for a tenant meant the specific (not time boxed or choosing a slot) time.  It is there job to resource against demand.

They developed an IT package (sadly, it didn’t take much programming – will Systems Thinking mean less work for software developers? I say, ‘probably’).  There are two columns, essentially Demand and Capacity.

Creating a trade supplies company (in the middle of a financial crisis!)

[Comserve set up MTS – multi-trade supply in 2008 in the middle of the financial crisis after the issues around trade supply they found when they studied the work during ‘Check’]

They found major problems with operatives having the right stock at the right time to finish the job.  Often the stock wasn’t in the van. Many times the tradesmen had to go to a trade supply.  Intriguingly there is often a burger van outside the trade supply store – showing how much time tradesman were waiting there! (1.8 hours a day per operative going to the trade counter – £560,000 a year!)

End to end cost – how much does it cost to supply a replacement bath? The focus was on getting on the cheapest bath, but often this meant the operative going past 2 or 3 stores, to go to a place to get a bath £5 cheaper! (a unit cost focus), not factoring in the £20 an hour the operative wasted driving past the stores to save the £5

Comserve tried to get another supplier to deliver stock to the operatives on site.  They had to set up their own database about what was used, by who and when. They then went back to the vans to review the stock that they had in.  Previously they’d had meetings about ‘what stock do we need in a van’ (without checking).  After 13 weeks of data, they realised that 75% of the stock in the vans wasn’t used. Of the top 20 items, they didn’t have 10 of them in the van! By studying and collecting data they were able to improve it to 85% of the van contents being used.

It wasn’t practical to have every piece of stock in the van. They realised that big items, such as baths, had a lead time (about 30 minutes), so they could get someone to deliver it, leaving the operative on site to keep doing useful work.  The operative rings ahead of time and says “I need a batch in 20 minutes” and the trade supply group deliver it.

They have capability measures.  An example of how often MTS were on time – how long do operatives have to wait? Sometimes a door can be taken off quicker than it can be delivered.  They know that people are waiting 256 minutes a day waiting for supplies.  They believe that they are now saving £245,000 a year even factoring in the costs of the delivery group.

Customer satisfaction wasn’t in a control chart because ‘it was a flat line’ at 9.93 / 10.  If it wasn’t rated a 10 we ask “why wasn’t it a 10?” this lets us look for trends that allow us to improve the service.

For the leaders, they have happy customers and an engaged workforce.  Management decisions are based on fact.  Without taking on more staff they have increased turnover 66% in 18 months.  They have new clients.

Seddon’s Summary

If you told repair organisations they shouldn’t work to standard times, people would say ‘that would be tricky!’ but Portsmouth shows it can be done.  When an operative gets to a house they phone in ‘how long it will take’. Most managers don’t trust operatives to make this decision – “they’d just bugger off if we let them do that”!”. Portsmouth have ‘designed for perfect’ around ‘optimising the system to fix the problem first time when we visit a house’.  The audit commission have downrated it because there are no benchmarking and schedule of rates – but would they have done this if they’d visit other people? Deming said ‘don’t copy without knowledge’.  Benchmarking is the fastest way to mediocrity and being like everyone else.

Question Session

Owen answered a question about how to introduce this with managers:

Managers thought that it was mad, because it didn’t fit with their MBA, so we had to help them with a ‘normative experience’. They did start by looking at Toyota, Virgin and Tesco who described themselves as ‘Systems Thinking’.  We put people through a 3 day crash course on ‘Lean fundamentals’ from Vanguard to build knowledge and learning. But it became clear that training wasn’t going to be as effective as doing; we needed to improve something.  So we started with something that involved customer focus, so that we could start measure or learn.  It wasn’t easy – you are trying to make this normal. It can’t collapse if a leader leaves the organisation. It took me a long time to work out that I needed to work out how to work on people’s thinking, not on what they do. It took 2 interventions to do this.  Even today, at Portsmouth, there are people who don’t think this is the right thing to do. Sometimes you just have to be tough and say ‘this isn’t an option, this isn’t a democracy, this is what we’re going to do!’

More from Owen:

The management are very focussed on reducing unit costs of phone calls, but they aren’t looking at why people are having those calls!

People in the organisation now want to know about Systems Thinking because they need to start saving, but they are 5 years too late to start achieving in-year savings.

In focussing on traffic wardens the focus was on reducing the number of people walking the street, because they ‘seemed to be doing the same thing’. But now, for example, if someone sees fly tipping they have to ring a call centre, that then have to send it out to another person on the street – all of this is activity that doesn’t related to helping the public, but what managers are focussing on is on reducing the cost of the call!

We aren’t trying to make services more efficient – we are trying to redesign them”!

Ian on how they collect data for their database:

Our data comes from the on-site operatives.  We’ve done away with PDA’s because we found they didn’t work. When they go to site, the time they are sent is logged.  They assess the repair on site and ring back to the call handlers to say they are on site and how long it will take (we’ve captured travel time automatically). When they are finished they say ‘this is what I did and what parts I used from the van stock’ (giving times for completion, parts used, number of operatives, number of visits to complete the repair).  All of the data goes straight into the database without using any paper forms.  We use these data (real data as Seddon says, not arbitrary things like targets).  The database is custom developed.  It took 3 weeks to write and cost £3,500! and this was with a 1,500 bonus to do it in 3 weeks rather than 4!

Owen on regulations in housing:

We asked users what they wanted, and they said they didn’t want the measure that the Minister wanted.  It was the same with choice-based lettings.  Choice ended up discounting those most in need because they weren’t savvy enough to handle the bidding process, so we told the minister we weren’t going to do it.  It got to a sessions where we said “Are you going to make it the law? If not, we’re not we’re going to do”. Sometime you need to have the fortitude to stand up to the minister to say “no, our residents don’t want this, were not going to do this”. Sometimes you just have to do what is right.

Did the efficiency savings reduce the oeprative’s pay. Ian answered:

All of our operatives are on salary so it’s had no impact.

Question: “If I said we’d do repairs when the customers want them, the manager would say we need a buffer of repairs to deal with peaks and the troughs”. Ian answered:

When we started doing repairs when customers wanted, there were peaks at 10am and 2pm with troughs in-between. This was a challenge for the first month or two, and we missed many promised times.  We found that we had two teams – repairs and voids (where one tenant leaves and it has to be fixed for the next tenant).  The void work now gives us this buffer. We have strict void times, and we make sure we get them done, but by blending them together. All operatives do repairs in the morning and then switch to voids in the afternoon, allowing us to meet customer demand on voids and repairs.  Also, block repairs help with buffering.  As an example, we used to take doors to site ‘unprimed’, but now in the downtime we have for painters and decorators we prime the wood up so that they go to site already (which takes out the peaks and trough for painters and decorators).  It takes 3 – 4 months to get a good enough picture of demand to be able to resource against it.

What happened to the managers? Owen answers:

None of the managers have left. The ones who had the locks on their doors changed are still there. One said “if you think that I’ll give up this office that took me 30 years to get, you’re dreaming” (Owen got the carpenter in). Now that manager says they now love being out in the work.  We’ve placed our managers to go through a normative experience to do interventions with Ian’s team (their outsourced supplier!).  Lots of people say ‘how can you resource this?’ but when you look at what their current job is they waste their time on meetings and e-mail.

Question about self-contained teams or clusters who are resistant? Owen answers:

We believe most people want to do a good job. You didn’t advertise for ‘negative, recalcitrant people’ – they turned up as good positive people.  What’s happened in the mean time? We have, giving them a system that didn’t allow them to do their job. We’ve found working on the system works.  When you start, you think it’s “people problems”, but after you realised

John Seddon: Starting ‘change’ by ‘studying’ isn’t sexy but it’s right!

John Seddon starts the Vanguard “Systems Thinking: The Leaders’ Summit”:

“It’s not very sexy to say we’ll start change by studying.  Managers like to do something, let’s start and do our ‘programs of change’.  ‘Let’s study’ is also rude because it implies we don’t know what’s going on. Deming used to say managers knew everything except how to improve.  He said you need help from outside, but really you need to have a different way of seeing and studying.”

There were some interesting discussions in the taxi about people being worried about this being an ‘evangelical event’ and that many of the videos of ‘success stories’ on Systems Thinking Review had people speaking about ‘how I was blind, but now I can see’.  It’s an interesting dilemma; if the results are counter-intuitive and people do go through a learning loop that feels like they can now ‘see’ how can you describe this to others without being evangelical? Also, how would you present this in a way that was vigilant against it becoming religious/evangelical?

Follow

Get every new post delivered to your Inbox.

Join 71 other followers