Solve persistent/chronic problems

EC-EVAPORATING CLOUD METHOD / CSR-CONFLICT RESOLUTION DIAGRAM / CLOUD

As Pain is a Pain and it needs to be taken care of and resolved permanently in the same way a Problem is a Problem and it must be taken care of effectively and that too well on time. There could be number of methods to resolve a problem and surely the right approach with the right implementation can only solve and cure the problem effectively and permanently.

Though there are number of methods but few of them looks very promising to solve persistent or chronic problems. One of them is Evaporating cloud method.

The Evaporating Cloud is one of the six Thinking Processes in the Theory of Constraints. The Evaporating Cloud (EC) - also referred to in the literature as "the cloud", or as a "conflict resolution diagram- is a logical diagram representing a problem that has no obvious satisfactory solution.

As the name tells, the Conflict Resolution Diagram (CRD) is used to surface and resolve conflicts, e.g. dilemmas.

CDR is based on conflict:

A conflict is anything which goes against your objective or your point of view. It is often seen that conflicts are resolved with a sense of compromise. The solution offered by compromising directs to a path which will not offer a sense of satisfaction.

Why conflicts?

A situation of conflict arises as a result of false assumptions, beliefs or myths. However, given the fact that two opposite things cannot be true at a given point of time, it is needleless to say that one is false or incorrect. If we can remove this myth or falseness, the conflict disappears which is known as evaporating cloud. This situation leads to a no-compromise and a win-win solution.

Resolving conflicts

There are two ways to resolve a conflict; either by considering two sides of an argument and second by injection (s) i.e. adding something, a solution, a remedy that didn’t exist in place.

The structure of a Conflict Resolution Diagram / Evaporating Cloud

A (simple) CRD is made of five entities (round cornered boxes) conventionally named A, B, C, D and D’.

          B(Need satisfied by D)  --à    D(Action you want to take to resolve)

A(Common Goal to B and C)

          C(Need satisfied by D’)           --à    D’(Opposite action of D)

Entity A is the common objective which requires B and C to exist; In order to have A, we must have B and C.D is a prerequisite to B (in order to have B, we must have D), while D’ is a prerequisite to C. D and D’ cannot exist or happen simultaneously, like for example attend a meeting in Rome and in the same time attend a conference in Berlin. In this case the conflict would be a dilemma choosing between the two events. D and D’ may not happen simultaneously because available resources do not allow it and the dilemma is about allocation of the scarce resource. Arrows are symbols of necessity relationship. In the same time the arrows are symbols for underlying assumptions, and as such can be true or false. But the assumptions are usually statements (beliefs) and/or justification for the relationship. The CRD’s purpose is to surface and test these assumptions. The broken arrow or lightning between D and D’ is the symbol for opposition or conflict.

Will be elaborating further in this methodology, so say tuned :)