12/26/2008
Step 5 – Think system To summarize the arguments of the first four steps: The major disease of modern organizations is in their design and management. If we want to achieve a quantum leap in performance, we have to be prepared to change the way we think. In Step 1, I exposed the problems associated with designing and managing organizations as top-down functional hierarchies. In Step 2, we began to look at the organization in a better way, from the outside-in. In Step 3, we looked at the idea of organizational capability – what is predictable about what is happening between you and your customers? And in Step 4 we studied flow – how your organization responds to customer demands, end-to-end. If you conducted the exercises as suggested you will have a diagram of the transactions with your customers, at each point of transaction you will have reliable data about what is currently happening and you will know the flow and waste or sub-optimization within it. Now we can move to the causes of current performance, the system.
Figure 1: Change management thinking The system governs performance It was W. Edwards Deming who first argued that the system governs performance. “Do not assume“, he said, “that people can be held responsible for performance, for their performance is governed by the system within which they work“. What does this mean? Consider, for example, the number of organizations that have invested in customer care training yet have found little or no improvement in the care their staff gives to customers. Generally, you find these people are not the problem; it is the system that won’t let them serve their customers. For example, · procedures people have to work to are written by head office, and from an ‘internal’ point of view; · measures people have to work to cause them to work against the customers; · the fact that managers are the only ones who can make decisions means people have to refer things, and so on. These things are all examples of ‘system conditions’; they govern performance. If you followed the exercise in Step 4, Think flow, you will have identified waste in your current flows; waste consumes resources. I find it helpful to remember that waste is a consequence of the way the work works – the way work is designed and managed – it is not and should never be treated as normal. We create waste; it is a consequence of the system and it is our responsibility. For example, · We carry excess inventory that never gets used. Why do we carry it? Just in case. · We re-work things that have not been done right the first time. Why do we have to re-work? Because we don’t know how to design quality in, we don’t know how to control work before it is done as opposed to controlling it after it is done – and the latter (inspection) just causes more waste. If you followed the exercise in Step 3, Think capabilities, you would have come across a particular and ubiquitous form of waste: ‘failure demand’. Failure demand is the label I give to demand caused by a failure of the organization to do something right for the customer. For example, customers call because they don’t understand their bill or they are having to followed-up (or chased) something that has not happened as promised. In most organizations you find this is treated as a normal part of doing business. Traditionally-minded managers don’t notice failure demand because they look top-down, not outside-in. Such managers are concerned with functions and their costs, they cannot see the causes of costs. Traditionally-minded managers use measures that encourage parts (functions) to ‘win’ while the whole ‘loses’; we often waste enormous amounts of human talent by engaging people’s ingenuity in surviving in or beating the system, rather than contributing to it. Thinking ‘system’ reveals all When you can see your organization as a system, warts and all, you learn about the ‘what and why’ of current performance. You can see what could be achieved and, moreover, you can see what needs to change to realize the potential improvements. Taking a systems view is totally different view from the traditional, hierarchical view. The traditional, hierarchical, view is to look at the organization as having parts or functions. The systems view is to look at the whole. This is more than understanding how the parts work together – that in itself being only a useful first step. For a systems view leads ultimately to systems management, an entirely different way of designing and managing work from the more traditional mass production view. Two simple examples: 1. How the parts work together If you have discovered that part of your organization is subject to high levels of failure demand, the first step would be to identify the cause – what part of the organization is not working right and causing this unnecessary demand? The next step would be to ‘turn off’ the causes of failure demand. Very good so far, but the next step is the ultimate systems management step: to establish measures of the type and frequency of demand such that the same problem will be identified as soon as it happens in the future. 2. How system conditions damage performance If you discovered in Step 4, Think flow, that the flow of work is damaged by functional measures, for example, people meeting their functional goals at the expense of the needs of the customers, causing re-work and other forms of waste, your next steps might be to size and remove the waste. But the ultimate systems step would be to remove the cause – to remove the functional measure that is driving the dysfunctional behavior – and to replace it with a measure that will encourage the right behavior (in most cases measures of capability – see Step 3, Think capabilities). These (systems) remedies frighten many managers. Managers frequently want to hold on to what they know; they understand functional measures – measures of budget, standards, activity and the like. While they can appreciate the damage being caused by the use of these measures, they are often reluctant to remove them and instead try to maintain that if used ‘sensibly’, these measures will help and thus should remain. If you have a dog at home, raise a rolled-up newspaper – don’t hit the dog – the impact is the same; and so it is with traditional measures. Measures are not the only system conditions that affect performance. Here are the other common ones: · Structure, · roles, · procedures, · information, and · job skills and knowledge. While the list is, in reality, more complex than that, I would encourage you not to worry about the potential complexity. If you have taken the steps I have outlined in this series – understanding demand, value, capability and flow – you will be looking into your system from the safe ground of knowing the nature of current performance and, hence, will be able to identify the particular system conditions that are affecting performance in your case.
|