Define the Problem Before Solving It: How to Resolve Conflicts Constructively
Using Evaporating Cloud Diagrams to Identify Underlying Assumptions and Reach Win-Win Solutions
In this article, we will learn how to constructively resolve conflicts so that they don't resurface in a slightly different form shortly after.
The great Einstein was asked: "If you have one hour to save the world, how would you spend that hour?" According to legend, he responded, "I would spend 55 minutes defining the problem and then five minutes solving it." While there is much doubt whether Einstein said this, defining the problem before solving it is widely accepted as sound advice. A quick Google search for "define the problem before solving it" yields over 485 million results, indicating that this principle is crucial in problem-solving.
Why define the Problem first?
So, why define the problem first? Defining the problem allows us to focus our efforts, resources, and time in the right direction. With a clear understanding of the problem, we can save resources on irrelevant solutions or even worsen the problem.
By defining the problem, we can clarify the goal, identify constraints, gather relevant information, and develop a plan of action. Defining the problem ensures that we focus our resources, time, and energy in the right direction, leading to more effective solutions and better outcomes.
Define the problem in case of a Conflict
Now, let's talk about conflicts. Conflicts can be found everywhere, whether it's at home or work. It's fair to say that conflicts are worth solving, but how do we solve them? We can solve conflicts by adding a step of first defining the underlying problem of the conflict.
We must look beyond the current actions and understand the underlying motives to do them. The visual Evaporating Cloud is a tool that helps us do just that. The Evaporating Cloud is part of the Theory of Constraints (TOC) Thinking Processes and is also known as the Conflict Diagram. It resolves conflicts by stating both sides of the problem and reviewing the underlying assumptions that create the conflict.
The idea behind the Evaporating Cloud is that as long as everyone has a shared goal, there cannot be an unresolvable conflict—instead, every perceived problem results from at least one faulty assumption. Therefore, if all conflicts are founded on false assumptions, removing the conflict requires identifying assumptions which are too often not voiced. Once we find the wrong assumptions, we can readily identify and permanently mend problems.
To define the problem of the conflict between two parties, we define the problem as follows. First, we start by identifying the shared objective. This sounds more difficult as it is: companies want to be profitable, couples want to be happy together, etc. If we cannot identify a shared objective, inventing one that both sides can agree is normally possible. Next, describe each party’s specific goals (or “needs”). Then we map out the specific actions of each side in the diagram ("wants"). The outcome will look similar to the diagram below.
Solve the Conflict
Based on this graph, we can identify the underlying assumptions that led to the conflict. Once we have identified the assumptions, we can challenge them and find a solution that satisfies both parties. The result is a win-win solution that is better than any compromise.
The visual model we've established serves as a tool to expose underlying assumptions. Therefore, it’s crucial to identify and examine these assumptions individually since each can guide the solution in a different direction.
If done correctly, both parties will endorse the solution, and the problem won't resurface in a slightly different form shortly after.
To give it more meat, let's look at an example. Let's look at a mid-sized specialised production business. A worker with special skills (let's say quality assurance of melding via X-ray) is sick for a few weeks and needs a short-time replacement. Imagine a finance department that needs to reduce costs and an operations (=production) department that needs to maintain quality. One side wants to pay less for the staffing, and the other wants the take the first good enough candidate. The conflict diagram would look like this:
An example conflict
We can see how the two departments want opposing actions and that they both want it for good reasons. So we could now start to compromise and agree on numbers, like: "We will interview five candidates, shortlist two and take the cheapest”, or "After one week of unsuccessful searching for cheap temp workers, Operations has free hands".
But there are better solutions than this. The best solution is to find the underlying assumptions. In this case, some underlying assumptions are:
Delaying onboarding can be absorbed by Operations. Just because it worked out in the past doesn't mean it will work out in the future. Even more so, there might be a hidden cost for paying overtime or losing a customer.
We can only find temp staff members after we need them. The formal contract with the right temp agency can solve this, or at least make it someone else’s problem.
Finding more Candidates takes longer. This is not necessarily true. We can use a temp agency or a headhunter to find more candidates in parallel. The only extra time it would cost is the time to interview the candidates. In most cases, this is a good investment.
The Diagram with the underlying assumptions would look like this:
These assumptions can resolve the conflict and fix the situation without compromise. Often they can be combined and create an even better solution. For example, we could agree to use two temp agencies we will ask in case of need and create a framework contract allowing us to onboard a temp worker within 48 hours, which is acceptable to Operations. This would solve the problem without compromise and be cheaper than the original solution.
We started with the idea that defining the problem before solving it is good. We then examined how to define the problem in case of a conflict. We saw that the Evaporating Cloud is a tool that helps us do just that. An Evaporating Could diagram represents the problem in a visual, condensed manner. The diagram supports resolving conflicts by stating both sides of the problem and allows reviewing the underlying assumptions that create the conflict. We then looked at an example conflict and saw how to use the Evaporating Cloud to resolve it.
We saw that the Evaporating Cloud is a powerful tool to constructively resolve conflicts so that they don't resurface in a slightly different form shortly after. Moreover, it is a tool that can be used in many situations, not only in conflicts.