A Guide to Implementing the Theory of Constraints (TOC)

A cloud is an elegant graphical means of displaying and solving an apparent conflict or dilemma between two actions.  It is also sometimes known as a conflict resolution diagram; however, its correct name is a cloud.


Central to the use of clouds as a problem solving device is the assumption that there are no conflicts in nature only erroneous assumptions.  "There must be an erroneous assumption that we make about reality that causes a conflict to exist (1)."


Lets look at this from another perspective and another culture Japan;  Problems exist because people believe they exist. If there were no people there would be no problems. People are also the ones who decide that a problem has been solved. Problem solving is the most typical human behavior (2).


The apparent conflicts that do arise and which we do want to solve are likely to be of two types (3);
1.

2.

Opposite conditions conditions that are mutually exclusive. Different alternatives conditions that preclude one another.

Day and night are mutually exclusive, more money or shorter hours are different alternatives.

We have been using clouds fairly liberally throughout all life. This should help to underline their intuitive nature.  We might use a cloud for everyday free-standing conflicts or dilemmas, or as a tool to resolve the core problem or core conflict made apparent as a result of the construction of a current reality tree.


You can learn to do clouds on the back of a piece of paper or in you head.  Such a skill can be a formidable advantage to the user.  The key point, however, is that you must want to solve your problem or dilemma. Without the will to solve the problem, the way to do it wont be apparent at all.


Countermeasures And Injections

The cloud is the tool of choice in seeking to obtain understanding and agreement on the nature of the core problem or core conflict, especially the unstated assumptions that give rise to the problem.  This is often described as the direction of the problem.


Breaking the cloud by developing an injection builds understanding and agreement on the direction of the solution to the problem at hand.  An injection is any new idea that we introduce into our current reality to produce a new and desirable outcome.


On the previous page we saw how Taiichi Ohno used the 5 whys method to drill down to the core problem Otherwise, countermeasures cannot be taken and problems will not be truly solved (4).  The countermeasures were his injection.


However, countermeasures are limited conceptually to mitigating a currently undesirable effect by removal or replacement with something else.  Injections go one step further they may in fact create a totally new and desirable step as well as mitigating the currently undesirable effect.


If the word injection doesnt do it for you, think countermeasure for the moment until you are more familiar with the concept of clouds.  Think of clouds armed with countermeasures as formidable weaponry.


The Cloud And The OODA Loop

The cloud is formidable, but it is also enigmatic.  It is used both to formulate the nature of the problem and also to formulate the direction of the solution.  Previously, on the page on agreement to change, we developed a composite 5 layer verbalization of the layers of resistance.


This is what we wrote;

1)

2)

3)

4) 5)

We dont agree about the extent or nature of the problem. We dont agree about the direction or completeness of the solution. We can see additional negative outcomes. We can see real obstacles. We doubt the collaboration of others.

We discussed the subdivision of layers 1 & 2 in more detail in the page called more layers accessed off the agreement to change page.  In essence we can subdivide layers 1 & 2 into two based upon Senges differentiation of detail and dynamic complexity;


a)

b)

1a) We dont agree about the extent of the problem detail complexity. 1B)We dont agree about the nature of the problem dynamic complexity.
 2a)

We dont agree about the direction of the solution dynamic complexity.  2b) We dont agree about the completeness of the solution detail complexity.

The current reality tree addresses the detail complexity of the extent of the problem.  The future reality tree addresses the detail complexity of the completeness of the solution.  The cloud, however, addresses both the nature of the problem and the direction of the solution.


As such it is a transitional tool or a pivot in the whole process.  If we accept that there are two distinct phases to the cloud it is much easier to understand.  We can draw a simple model of this situation.


hola

The sequence; what to change what to change to, is drawn as a closed loop a process of on-going improvement.  Essentially it is a decision loop addressing the problem and the solution without going into the detail of executing the solution.  We can see that the cloud is the pivotal part of this construction.