Theory of Constraints Handbook - James Cox Iii [486]
Very often, the need in C—as recorded by this person—will be representing the need or views of another function of the organization.
However, if we are in a group consensus activity it may be that this “other function” is a member of the group doing the consolidation. He or she may see and agree with the same UDE, but from their point of view it endangers their B. Therefore, we can have the same need that appears in one Cloud in the C box and in another Cloud in the B box. Both needs have connections to their corresponding tactics. Hence, we have a situation that B-D is of the same pattern as the C-D′ of another Cloud. Knowing that this may happen, we have to review the three Clouds before starting the consolidation step.
Example:
UDE #1 We often do not have sufficient capacity to meet all demands.
In Cloud #1, this UDE was perceived as endangering need: “Meet our production schedules” that was recorded in box B.
This is a valid need of the Production Manager who is measured against meeting the production schedules.
However, from the point of view of the Sales Manager, the same UDE may endanger a different need (that is currently recorded in box C in UDE Cloud #1): “Satisfy customers, increasing demands.”
And thus while building the UDE#1 Cloud the Sales Manager may put in B the current wording from C, and in D the current wording from D′ and thus his Cloud will look “flipped.”
For the Production Manager, the need that is endangered is the production schedule and the other need to be considered is to satisfy the customers’ demands. The Production Manager’s view is shown in Fig. 24-12
However, when this Cloud is written from the point of view of the Sales Manager, the same UDE “We often do not have sufficient capacity to meet all demands” endangers the need to satisfy the customers and hence it will appear on the Sales Manager’s B-D side of the Cloud. The Sales Manager’s view of the endangered need is shown in Fig. 24-13.
In order to consolidate the views of both managers, we have to “flip back” the sides of the flipped Cloud.
While observing the Cloud before consolidating, we can identify the nature of the needs in the Cloud. One is dealing with the needs of production and the other with the needs of the customers and presented by the sales function.
FIGURE 24-12 Example—UDE #1 Cloud from the production manager’s point of view.
FIGURE 24-13 Example—the endangered need from the sales manager’s point of view.
The Relationships between the Consolidated Cloud and the Core Cloud
The Consolidated Cloud explains the existence of three (or sometimes more) of the chosen UDEs in an area. The role of the Core Conflict13 Cloud is to explain the existence of the majority of the UDEs and the inherent conflict that prevents sorting them out.
Although the Consolidated Cloud points us in the direction of the core Cloud, the analytical work that was done to reach the Consolidated Cloud may not be enough to guarantee that it is the core Cloud because the outcome of the consolidation process may be skewed by the selection of the UDEs.
The following process can be used to verify that the Consolidated Cloud can serve as a Core Cloud:
1. Take another UDE, develop the UDE Cloud for it, and check if the Cloud fits the pattern of the Consolidated Cloud. A fit means that A, B, and C are about the same verbalization and D and D′ are of the same nature of the D and D’ of Consolidated Cloud.
2. Repeat the same step for all the other UDEs.
3. If a fit is found, the Consolidated Cloud can be used as a core Cloud (if at least 70 percent of the UDEs are represented by the Core Cloud).
4. If in the previous steps a UDE Cloud (or several UDE Clouds) does not fit the Consolidated Cloud, then a further consolidation is done by repeating the consolidation process for the UDE Clouds that do not fit together with the Consolidated Cloud. The result of this step can be called “double Consolidated