Category Archives: Process Improvement

Systems ignorance and unintended damage

Cause and Effect Analysis is often considered a comprehensive approach to addressing problems and identifying solutions. This approach is true in closed systems where linear cause-effect relationships typically occur. Many areas of manufacturing and assembly would fit into this model.

Most work situations do not occur in a closed system but instead are in open systems where many factors affect an outcome.

Ishikawa recognised this in his ‘fishbone analysis’ approach to problems. He recognised that many causes, and layers of causes  can affect an outcome. He also advocated for the collection of data on causes and outcomes before relying on an intervention to have a desired affect.

If we ignore this advice we will implement actions which will have unintended consequences. Send a ‘communication’ and it is interpreted as a threat. Give a pay-rise to one person and it is seen as a betrayal of trust by a dozen other people. Instigate an inspection system and it generates a new industry (and associated cost) to the sector. Seek to drive down costs by reducing resources and it will increase costs by causing repeated failures.

If you have a lunchtime to spare it is worth listening to Peter Senge’s discussion about systems in organisations:

Peter Senge’s keynote speech “Systems Thinking for a Better World” at the 30th Anniversary Seminar of the Systems Analysis Laboratory “Being Better in the World of Systems” at Aalto University, 20 November 2014.

Leadership lessons from Deming

It is 90 years this month since Ed Deming completed his PhD in Physics, but it is his work with statistical understanding of processes and performance of organisations, and its impact on human behaviour and leadership which is his lasting legacy. Deming was alays open to learning new things, up to the end of his life at the age of 93 – a lesson for us all.

A few important concepts which he identified for leaders include:

  • 90% of problems are cause by the system – and the system belongs to management
  • Banish any form of individual ranking or reward because 90% of variation is due to the system and not individual performance.
  • There is no substitute for knowledge. Seek knowledge not opinion or assumption.
  • Engage people in change. From day-to-day activity they know the problems and issues of work better than managers. Give them the measures to understand the activity and they can better make efforts to improve it.
  • Best efforts tend to cause problems. If we just ‘try harder’ it is likely to make things worse, unless we change the system of work
  • Drive out fear. Innovation, ideas, creativity enable high work performance. Fear crushes all of these things.

Reading:

Deming W.E. (1982) Out of the Crisis, MIT CAES, Cambridge MA.

Deming W.E. (1993) The New Economics, MIT CAES, Cambridge MA.

Voehl, F. (1995) Deming the way we knew him. St Lucie Press, FLA

 

Costs are found in flow – not within activities

 flow2To reduce costs, the expectation is that we must ‘gain efficiency’. This means speeding up the activities which we carry out or reducing the amount of money spent each time we do it. To understand the speed of activities, we should (surely!) count those activities or their cost – and perhaps see how quickly they are repeated or how much cost they accrue. Does this make sense so far?  If it does, then you have been led down the garden path.

Meaningful change should relate to the purpose of the team (essentially their focus on the work), and the team’s purpose should fit with the wider organisation’s purpose. Efficiency gains mean nothing if purpose is compromised. Even cost savings to save a business must be purposeful (and related to core business) if that business is to have any chance to succeed in the long term – otherwise it is just giving respite to an essentially lost cause.

Next consider whether your change is going to impact/intervene with the task (work), the team, or a particular individual (or individuals).

  • With task changes you are interested in both the value of the task (output quality as assessed by the user) and the flow of the activities (timeliness and waste/repetition/failure recovery etc).
  • With team you are looking at effectiveness of contribution and team energy, morale, sharing, learning, synergy and interactions.
  • With individuals it is about their contribution, development and commitment.

If people have been brought along with the change, the reasons, how it fits with team purpose and how it improves output for users at less effort for us (or at least, less wasted effort), then you are much more likely to avoid problems with ‘team’ and ‘individual’. So in a roundabout way a holistic view is important. But it is important at the outset  – during the design of your intended change (when you consider what /where/when) and how you design the ways in which  to get people on board in that design.

The reason people get bothered by change is either:

1) because they know the work and can see the pitfalls and would prefer to implement changes that would make a real difference (potential positive constructive contributors), or

2) they know the pitfalls and want to hide them because they should have raised those problems themselves, so feel a bit exposed (likely negative grumblers).

The ‘1’s will be in the majority – you need to make sure those people don’t become grumblers because their input has not been sought or valued!

 

Reading:

Adair, J. E. (1973). Action-centred leadership. McGraw-Hill.

Seddon, J. (2003). Freedom from Command and Control. Buckingham: Vanguard Press.

Change can’t be planned – it emerges

Traditional change management follows a linear approach, defining a goal, identifying a plan and delivering to that plan. The process is logical and surely unquestionable. The approach to setting targets for change and measuring progress now has its own name ‘deliverology’ – but this does not change traditional linear thinking.

The problem is that organisations do not act in a linear fashion, they are much more complex systems. This means that if you change one thing then something unexpected is likely to happen somewhere else – and what you had intended may or may not happen.

Of course understanding systems can be a difficult thing to do. Instead managers either resort to ‘giving their view’ on things, or  setting success measures, kpi’s and so on, based on those views. Having a view on why things are a problem is one thing, but  for John Seddon, it is better to get knowledge by collecting data.

He suggests that it is better to define the following:

  • Purpose is the definition of why we are here, best understood from the customer (or user’s) perspective.
  • Measures allow us to understand what is likely to happen going forward if the systems doesn’t change.
  • Method – can be addressed when we understand the data derived from our measures.

Systems Theory tells us that Purpose Measures and Method are fundamentally linked – it is a systemic relationship. This systemic relationship can either work for you or against you depending on how you set things up.

If you impose arbitrary measuresyou create a de facto purpose, which is the one that the workforce will follow. This will constrain method. It will prevent people from improving the work.

On the other hand if you derive measures from the users point of view (e.g. customers)  and then put those measures in the hands of people doing the work you and enable people to improve method so that measurable improvements can be pursued, then you can systematically deliver success.

The paradox is that in this system, change requires no plan. For Seddon, change is simply an emergent property. Innovation can only occur if you set things up that enable people to innovate in response to the real system of customers and organisation – what happens.

Any attempt to plan change otherwise is fiction.

Instead Seddon suggests that you need to see your organisation as it really behaves – how things work relative to your purpose ‘warts and all’ – because then at least you will know. Once you know that you can respond by innovating – enable people to innovate and overseee the changes that need to happen and you will improve morale.

John Seddon speaks briefly about innovation and change.

 

 

Targets only motivate people to meet the target (not to do good work)

The reasons for employing people are:

1) to do the work (produce output, product, service), and

2) to improve the work.

If the person is clear about the purpose of their work, then 1 and 2 should be easy to deliver if they have the right resources, skills, and understanding of users’ (e.g. customers) needs.

But managers rarely leave it at that…

Traditionally, managers get people to do ‘better’ in their work by what John Seddon tags as ‘sweating the labour’ – getting the people to work harder or faster. The idea is that you get more output for the same hours work – essentially more for the cost (efficiency).

Of course the idea of the sweatshop is morally uncomfortable – exploitation to achieve a profit motive. Yet we still stick to the idea by setting targets: ‘You produced 100 widgets last month, let’s have you aim for 110 widgets this month‘.

It seems plausible – motivational even! What possibly could be the harm in setting a target?

Well, the widgets are being created for a purpose – presumably the purpose for which the customer buys them. And that purpose is associated with the design and quality if production in the widget that is produced.

If you create arbitrary targets (and measures of performance) you will create a de facto purpose in people’s mind which is to deliver those targets. This is different from actually delivering the purpose of the work.

Your worker will work to produce 110 widgets BUT not necessarily a widget that meets the customer needs, nor a widget that could be produced faster or at lower cost whilst still meeting the customers needs, other than by cutting corners (lowering quality or increasing risk). The worker is busy but has got his eye off the ball. This produces errors and lowers the quality of work – which will probably have to be redone – at greater cost.

Targets are not motivational. They might make people move, but that is not motivation. A dog that moves is just one looking to avoid the next kick. It is not a motivated, free thinking, creative, proactive animal. Why would we exect people to operate any differently?

Reading

Herzberg, F. (1968) “One more time: how do you motivate employees?”, Harvard Business Review, vol. 46, iss. 1, pp. 53–62

Seddon, J. (2005) Freedom from Command and Control, Vanguard Press, Buckingham, UK.

Don’t do it to people

vader
One person’s management hero is another’s villain

Management involves getting the most efficient utility from people and resources;

Leadership involves getting people to do things they would not otherwise choose to do.”

EVEN IF TRUE
DOES THAT MAKE IT RIGHT?

In a nutshell the statements on management and leadership summarise conventional wisdom  accrued since 1900, first through the ‘scientific management’ methods of Frederick Taylor and later the alternative ‘human relations’ approach advocated by Elton Mayo. The latter’s approach was apparently set to counteract the rigidity and hierarchies of the former. Unfortunately both approaches have the same defective focus – ‘doing it to people’. They are both a reflection of a command-and -control mindset which many would percieve as ‘managerialism‘.

Improvement comes from understanding the system and making meaningful improvements to ensure better outcomes. Doing it to people does not achieve this. Whilst efficiency in car manufacture  increases, so do the additional costs of salaries to compensate boring jobs, and industrial relations and (at best) static levels of quality – in other words total costs go up.

Whilst most managers and leaders do not want to be working for the ‘dark side’ and genuinely want the better for their teams, they must understand that if they follow the scientific/human relations approach the consequences of their actions are: de-motivation, a loss of dignity, a diminished sense of purpose, and reduction of productivity in their staff.

In knowledge industries, additional contributions to the total cost of this disruption is hidden, for example losses of skilled workers, high staff turnover and recruitment and so on.

The choice is clear: managers and leaders need to find a better way…

Reading:

Hanlon G. (2015) The Dark Side of Management: A secret history of management theory, Routledge

Roscoe, P. (2015) How the takers took over from the makers. Times Higher Education, 26 November, p48

Seddon, J. (2003). Freedom from Command and Control. Buckingham: Vanguard Press.

Avoid the ‘bolt-on’ management method

Maybe not the best way to improve management

Sometimes approaches to managing people simply do not work. However, I have heard people defend the failure of particular management approaches (like appraisal, ISO9000, quality circles etc.) by saying ‘its because it is not being done right‘. While this may be ‘true’ (in the sense that successes can occur), I think that a more circumspect approach must be taken when considering these methods:

  1. If it doesn’t’ work, is this failure a generally observed occurrence? (i.e is it something that predictably fails)
  2. Is it only failing on an unusual, ‘exception basis’ – once in a while?
  3. Might the approach be fundamentally flawed?
  4. Could there be a better way of achieving the desired outcome (assuming the desired outcome is genuinely that the manager wants to do a better job of managing) – in other words is the well-meaning manager barking up the wrong tree?

The problem with bolting ‘good’ approaches onto bad is that it proliferates the work of management, which adds cost, hassle and meddling with the real work (of serving customers, providing public services, educating, making cars, or whatever is our business).

Treating people well, usually involves doing something (‘nice’) to compensate for the default situation, where they suffer some sort of indignity, disappointment or frustration as the general state of affairs. The ‘nice’ idea masks the fundamental problems.

John Seddon openly criticises this type of woolly thinking – not because he thinks people are not worthy of being respected and treated with dignity, but because the respect and dignity should start in the way that their work and the system they work within is managed. In other words:

  • don’t punish people for things out of their control,
  • don’t design work to frustrate them from doing a good job,
  • don’t waste their time.
  • don’t make systems which expose them to unnecessary grief
    (from customers and users)

Deming used to talk about dignity (long before most others used the term) and, as shown throughout his writing, appears to assume that everyone would be following the same ethos. Doing a ‘respect for people programme‘ would, to Deming,  be absurd. Just as doing appraisals would be absurd, or adhering to standards, or setting targets. What do these approaches say about what managers really think about their staff (lazy? untrustworthy? unmotivated? stupid?)?

Some things in life are worth restoring and refurbishing, even upgrading. But others are just so fundamentally flawed that an upgrade is not worth the effort. The same can be said for many management methods.

Just make sure that you are not applying bolt-on management.

 

Helpful reading:

MacDonald, J. (1998) Calling a Halt to Mindless Change, Amacom, UK

Seddon, J. (2005) Freedom from Command and Control, Vanguard Press, Buckingham, UK.

 

However, the alternative perspective is offered by Bob Emiliani:

http://www.bobemiliani.com/kudos-to-john-seddon/

 

Happy staff, happy work ; happy work, happy staff

santaTo paraphrase Richard Branson, ‘happy staff = happy work’, and for Branson, that means that customers will also be happy and your organisation will be successful.

Motivational theory and systems theory tells us that a work (the way it is designed and the constraints placed upon people doing it) also influences whether people are satisfied with what they do. In other words, happy work creates happy  people.

Deming talked about dignity in work decades before it became a focus of attention in Human Resource departments. His philosophy was ‘centered on people and the dignity of work. He believed that people should have joy in their work, that the system within which they work should be designed to make this possible and to enable workers to reach their full potential to contribute to the enterprise‘ and that system is management’s responsibility (Tortorella, 1995).

So for happy also read ‘joyful‘. Quite an expectation! But consider this: whilst a happy person is satisfied, a joyful person brings renewed energy and vigour into their activities, interests and relationships – exactly what we need in a high performing team. And a joyful person can be as quiet and dignified as they wish, or as outwardly enthusiastic as they wish, but their joy will rub off positively onto the people around them.

It is motivation…for free.

Reading:

Oswald, A.J., Proto, E. and Sgroi, D. (2014) Happiness and Productivity. http://www.econstor.eu/bitstream/10419/35451/1/522164196.pdf

Nazarali, R. (2014) Happy People are more Productive. http://ridiculouslyefficient.com/happy-people-are-more-productive/

Raymundo, O. (2014) Richard Branson: Companies Should Put Employees First. Inc.com, OCT 28, 2014. http://www.inc.com/oscar-raymundo/richard-branson-companies-should-put-employees-first.html

Seddon, J. (2003). Freedom from Command and Control. Buckingham: Vanguard Press.

Tortorella, M.J.  (1995) The Three Careers of W. Edwards Deming. Siam News https://www.deming.org/content/three-careers-w-edwards-deming

 

‘Value’ versus ‘Waste’ – why bother?

If we want to make improvements at work we  need to balance between two sets of action: reduction of waste and addition of value. William Sherkenbach reminds us that waste and value are NOT reciprocals

– you can reduce waste but not add value;

– you can add value but not reduce waste.

You need to do both in a balanced way.           The reduction of waste does not ensure value.

This is why John Seddon always starts discussions around improvement by asking people to understand what is happening first; how much good work they produce (the stuff that people want) and what it is (why it is valuable), how much waste is produced (stuff that is not what people want) and what types of waste. Seddon calls these the WHAT’s of performance. Only once we know what is happening can we differentiate value from waste (or  ‘failure demand’ as Seddon labels it). What is interesting is that by examining demand properly we can identify those things which on the surface appear to be a customer requirement (e.g. a request for a service or a query) but can actually turn out to be driven by a failure earlier in the process. If these things are identified we can flush out built-in failures in the design of systems, procedures and policies.

To some degree or another, a given production of good output (value) will generate a parallel degree of waste. If you double the output (good things), you will double the waste output (at the very least, aside from errors due to additional pressure on people and machinery). To improve quality of output (i.e. to get proportionally more good stuff) we need to redesign the system. Identify value and eliminate waste and failure.

An analogy is water consumption. If you find a new source of water and make it available for consumers to use, but don’t fix the leaky pipes, you will just generate more leaked water. A good water system has good supply of water and a continually diminishing occurrence of leaks. Water service professionals are concerned with water catchment (source and supply channels) and the integrity of the distribution network (fixing leaks).

However, taking the idea further using a different analogy, an economical way to run a car involves a combination of maintenance and driving technique for improved fuel efficiency, or a person could simply drive the vehicle fewer miles. How you carry out your driving relates to purpose. If we only drive a few blocks to buy a pint of milk, our decision about the car’s fuel economy might be different compared to someone who uses the car to commute 100 miles per day to work. Or, if we only want to take our prized sports coupé out at weekends in the summer to impress people at parties, the decision will be different once again.

Purpose is defined by the needs of the user. The ‘user’ is the user of our product or service. But also remember that ‘purpose’ should not exist in its own bubble. If we buy a Harley Davidson motorcycle just to use it to cruise in the sunshine on Sundays, that might be just fine. However, if we ‘rev it up’ every Sunday morning as we start our trip to the seaside, the neighbours might have something to say about it.

Purpose, value & waste. The start for discussions about performance is to understand all three.

 

Further Reading:

Seddon, J. (2005) Freedom from Command and Control, Vanguard Press, Buckingham, UK.

Sherkenbach W.W. (1991) Deming’s Road to Continuous Improvement, SPC Press, Knoxville, TE

Change and work: more misplaced assumptions

Conventional wisdom has tended towards considering change in the context of ‘programmes and projects’. However this approach does not easily lend itself to embedding change into day-to-day work. For example a common misconception is to use ‘training’ as a method to secure change, when other influences need to be addressed first. A second commonly ineffective method is to use ‘communication’ (telling people about the change), but this will have little impact in terms of real change.  Leandro Herrero (2006) recognises this misconception and suggests that the most important focus should be on behaviours. Seddon (2005) emphasises that work behaviour driven is by a change in thinking; how we see what we do and why we do it.

The change of perspective is subtle but important; for example there is the misconception that “New processes and systems will create the new necessary behaviours.”  Herrero (2006) suggests that instead it is new behaviours that are needed FIRST  to support new processes and systems. If you change a system first, people will adapt their behaviour BUT it may not be the behaviour that you want – it will depend on a variety of other factors. If you s=get the thinking right first then the design of improved systems will follow.

This brings us to challenge a third misconception, “People are rational and will react to logical and rational requests for change”; often we are individually and collectively much more complicated. Instead, people’s behavioural changes only happen if they are reinforced; leaders need to walk the talk and be consistent in the way they prioritise, make decisions and use resources in line with the change they expect to see (Seddon 2005).

Part of this is to embed continuous improvement and a culture where change is expected – a normal part of work. This is change with purpose, seeking improvement (rather than change for change’s sake). This contradicts a further misplaced assumption that “After change you need a period of stability and consolidation”  – on the contrary, we need a culture of continuous improvement, involving an on-going dialogue about what works and what doesn’t work and a mentality that makes things happen. Establishing these new behaviours as a routine means that momentum can be maintained.

Change is a balancing act!

 

Read more on change…

Herrero, L. (2006) Viral Change, meetingminds, UK.

Seddon, J. (2005) Freedom from Command and Control, Vanguard Press, Buckingham, UK.