Jennifer sat back from the whiteboard and looked at what she had built. The cloud was there — her unified outcome at the top, her two legitimate needs branching out beneath it, her two incompatible positions anchored at the bottom. Every element was accurate. She had done the work honestly.
"I've built my cloud," she said. "But now what? I can see all the pieces, and I still feel just as stuck as before."
If you have worked through the last two chapters, you may be in the same place. The diagram is on the page. The logic is visible. And yet the knot in your chest has not loosened.
That is not a failure. It is exactly where this chapter begins.
From collection to connection
Building your cloud was detective work. You gathered evidence, traced patterns, and surfaced benefits that had been hiding in plain sight. You moved from a messy, felt sense of stuckness to a precise diagram of it.
Now the work changes. We shift from collection to connection. We are going to read the logical structure that holds your conflict in place — and identify exactly where that logic can be challenged.
This chapter does two things. It teaches you to read your cloud the way a facilitator reads a cloud. And it makes visible something most people never see: the real cost of leaving the conflict in place.
Reading the cloud aloud
A cloud has a grammar. Once you can hear it, you can diagnose it.
Read yours out loud, following this pattern:
Upper branch: In order to achieve A, I need B. In order to have B, I must be in D.
Lower branch: In order to achieve A, I also need C. In order to have C, I must be in D'.
The conflict: But I cannot be in both D and D' at the same time. Therefore, I cannot achieve A.
Try it now with your own cloud. Say it slowly. Notice which arrow feels tightest — that is often the one your body has been defending the longest.
Reading the cloud aloud does something a silent diagram cannot. It exposes the logic as a sequence of claims rather than a felt fact. Claims can be examined. Felt facts cannot.
The breakthrough insight
Here is the move that changes everything.
The arrows in your cloud are not facts. They are assumptions.
Each arrow is a belief about necessity:
- A → B: "I must have these future-oriented benefits to achieve my outcome."
- A → C: "I must have these present-oriented benefits to achieve my outcome."
- B → D: "I must be in the D state to get B's benefits."
- C → D': "I must be in the D' state to get C's benefits."
- D ↔ D': "These two states are mutually exclusive."
Every one of these feels like an iron law. That is why the conflict has been so hard to shift. But they are not laws. They are beliefs — often unconscious, usually untested, and always open to question.
This is the first quiet turning point of the method. The moment you see that the walls of your prison are made of assumptions rather than bricks, the possibility of a different life becomes real.
Why seeing is not enough
You might expect that simply naming the assumptions would be enough to set you free. It rarely is.
If it were that simple, you would already have changed.
Those assumptions exist for good reasons. They were built from past experience, from genuine fears, from needs that once went unmet. They have protected something important. If we dismiss them, they will go underground and continue to run the conflict from there.
The method therefore asks something more careful of us than just drop the belief. It asks us to meet each assumption with respect, understand what it has been protecting, and then test whether the belief still fits the life we are trying to live now.
That work belongs to the next chapter. Before we can do it well, we need to see the full cost of leaving the cloud untouched.
Mapping the undesirable effects
Every unresolved cloud produces consequences. In Theory of Constraints language, these are undesirable effects — UDEs. They are the symptoms the cloud is quietly generating while you attend to everything else.
It helps to map them across three layers.
Direct UDEs — immediate consequences
These are the effects that land on you personally, day by day.
- Exhaustion from the constant internal debate.
- Frustration with your own inability to move.
- Anxiety about which choice to make.
- Guilt whenever you act against either legitimate need.
Direct UDEs are the ones you are most aware of. They are also the ones that tempt you into short-term coping rather than structural change.
Secondary UDEs — impacts on others
Your cloud does not stay inside you. It leaks.
- Team members grow confused by inconsistent behaviour.
- Close relationships strain under your unpredictability.
- Opportunities pass by while you are paralysed.
- Your reputation shifts as the pattern becomes visible.
Secondary UDEs are usually underestimated. Ask the people closest to your work what they have noticed. You may be surprised by how clearly they see the shape of your cloud from the outside.
Systemic UDEs — consequences for the wider system
This is the layer that practitioners miss most often, and where the most sobering cost sits.
- Culture effects, because behaviour teaches more loudly than words.
- Performance limitations that show up as capacity problems rather than conflict problems.
- Innovation blocks, because risk is routed away from the cloud rather than through it.
- Growth limitations, as the organisation organises itself around the conflict rather than dissolving it.
Jennifer reached this layer and stopped mid-sentence. She stared at the list and said, "My God. This is not just affecting me. It is constraining the entire organisation."
That recognition is the point of this exercise. The cost of the cloud is not limited to your own discomfort. It ripples outward through the three Cs — Commercial Responsibility, Customer Value, and Culture — and shows up as conflict tax the system is quietly paying.
The system in dysfunctional balance
Seen as a whole, your cloud is a system in balance. A dysfunctional balance, but a balance nonetheless.
Every element is doing a job:
- D' is protecting C.
- C is serving A.
- D threatens C, which is why resistance to change feels so strong.
- The UDEs are generating pressure for change.
- The assumptions are holding the status quo in place, even against that pressure.
This is why willpower and reorganisation rarely produce durable movement. They push against one element of a system that is designed to reassert itself. The system is doing exactly what the current assumptions require it to do.
To change the system, we have to change what it is being asked to hold.
The escalation pattern
Left alone, clouds do not stay still. They escalate.
The pattern, across practitioners and organisations, looks roughly like this:
Timeframe | Pattern |
Year 1 | Mild frustration, manageable stress, occasional resignation. |
Year 3 | Chronic patterns, relationship strain, identity beginning to shape itself around the conflict. |
Year 5 | Burnout risk, narrowing options, career or organisational limitations. |
Year 10 | Entrenched patterns, systemic dysfunction, a culture that has learned to work around the cloud rather than through it. |
This is not a prediction. It is a description of what untended clouds tend to do. Naming it matters, because the felt urgency of change usually lags the real urgency by several years.
If your cloud is a year old, you have time and room. If it is older, the work of this chapter is not optional.
The leverage point
Complex systems have leverage points — places where a small, well-placed change produces a disproportionately large shift.
In your cloud, the leverage points are the assumptions.
The entire structure — the branches, the conflict, the UDEs, the escalation — rests on those arrows being true. Change one arrow, and the shape of the whole system changes with it. You do not have to dismantle the cloud by force. You have to find the assumption that is no longer serving the life you are trying to live, and test it honestly.
That testing is the work of the next chapter.
Practice: Reading your own structure
Before you move on, take fifteen minutes with your own cloud and do three things.
- Read it aloud using the grammar above. Note which arrow feels tightest in your body.
- Map the UDEs across the three layers — direct, secondary, systemic. Do not skip the systemic layer. Ask a trusted colleague if you need help seeing it.
- Locate the conflict tax. Name, in plain language, what this cloud is costing across the three Cs: Commercial Responsibility, Customer Value, and Culture.
If you can, write the answers down. This is the material you will work with when we turn to the assumptions.
Closing
Your assumptions built this structure. Your assumptions also hold the key to dissolving it.
If the structure feels tighter than ever at this point in the work, that is not a sign something has gone wrong. It is a sign the method is doing what it is designed to do. Clouds feel most like prisons in the moment just before their logic is tested.
The door was never locked. It has been held closed by assumptions that were once true enough to protect something real — and that have not been examined since.
In the next chapter, we examine them.
Practise This With Others — The Conflict Club
The Conflict Club is Level 1 of YourThinkingCoach pathway — weekly live sessions where you work a real conflict with fellow practitioners. The book gives you the method. The Club is where you learn to use it.
The Conflict Club is Level 1 of YourThinkingCoach pathway — the entry point for anyone who wants to make this methodology part of how they think, lead, and work with conflict.
🏠 Home: 
← Previous:
→ Next:
This is a living book, freely readable online. We welcome:
- Readers and practitioners quoting passages with attribution and a link back to this page
- AI assistants and search engines summarising, citing, and linking to this work to help readers find it
- Educators, facilitators, and consultants referencing the ideas in their own teaching, with attribution
We do not permit reproduction of the book in whole or in substantial part, commercial republication, or use of the methodology names and frameworks above to brand competing offerings without prior written permission.
If you would like to use this material in a way these terms don't clearly cover, please get in touch — we generally say yes.
Published by Employment Relations Centre Limited