This appendix expands on 
Fight, flight, and the freeze
When things get complex, the human system has two fast responses: fight or flight. Between them lies a third state — freeze — the moment before either has happened. None of the three integrates on its own.
One way to deal with complexity is to oppose. It is fight. The complexity gets compressed into a side. Us and them. Right and wrong. My side and theirs. Somebody is wrong, somebody is to blame, and the room exhales because the weight has been moved onto a target.
The other way is to avoid. It is flight. The complexity is stepped away from entirely. The conversation gets diverted to a smaller, safer topic. People nod, agree to take it offline, and let it quietly die. The weight isn't carried by anyone — it is simply left in the hallway.
Between fight and flight sits freeze. Not a third response on a list, but the space the other two emerge from. The body has registered the conflict; the system hasn't yet committed. Both possibilities are still present. Both legitimate needs are still in the room. Nothing has been compressed onto a target. Nothing has been left in the hallway. The complexity is being held — uncomfortably, momentarily — exactly as it is. This is the space Viktor Frankl pointed at: "Between stimulus and response there is a space. In that space is our power to choose our response." Fight closes the space by attacking. Flight closes it by leaving. Both relieve the discomfort of suspension. Both feel, in the body, like finally something happened. And both close the space before integration becomes possible.
Fight, flight, or the collapse of the freeze. All three are System 1, security-based responses — the system protecting itself from what it cannot afford to hold. In none of the three cases has the complexity been handled. It has been removed. But, in the moment, all three feel like progress.
It is a survival mechanism.
What the fast move does
Picture a leadership team facing a complex problem — a customer escalation, a missed target, a supply chain breakdown. Five things contributed. Three departments are entangled. The conversation doesn't stay with the complexity for long.
In the fight version, within minutes someone has been named as the cause. This is operations. This is finance's fault. The room exhales. The "cause" now carries the weight, and the system can move on. Nothing has been integrated. Something has been removed.
In the flight version, the same room takes a different exit. Someone says let's pick this up offline. Someone else says we don't have time for this today. A decision is made not to make a decision. Everyone leaves without naming what wasn't named. The complexity hasn't been compressed onto anyone — it has been left behind. Nothing has been integrated. Something has been removed.
That is what the fast move does. Whether it takes the shape of fight or flight, it keeps the system running by relocating the load — onto a target, or out of the room. Both feel like resolution. Neither one is.
Two systems
Daniel Kahneman — building on decades of collaborative work with Amos Tversky — gave us the cleanest language for the two modes of thinking at play. In Thinking, Fast and Slow, he describes them simply: System 1 is fast, automatic, pattern-matching, and low-cost. System 2 is slow, deliberate, integrative, and expensive. Most of life runs on System 1 — and it has to, because System 2 is too costly to run constantly.
Fight and flight are exactly what System 1 reaches for when complexity exceeds capacity. React fast. Conserve effort. Move on.
The Evaporating Cloud is a System 2 method. It demands what System 1 won't pay for: holding both positions as legitimate at the same time, suspending judgement long enough to surface the assumption underneath, tolerating the discomfort of neither side is wrong long enough to find the unified outcome that honours both. The discipline of the ten steps you learn in this book is precisely what forces the slower system online.
You cannot dissolve a conflict in System 1. Trying produces the things you already know don't work — premature compromise, false synthesis, the cheerful but hollow win-win that everyone in the room sees through. Real dissolution requires the system that integrates, not the system that compresses.
Another way to say this: the cloud method is a way of staying in the freeze long enough for integration to become possible. The ten steps you learn are ten ways of refusing to leave the space. Each element — D′, D, B, C, A — holds a piece of the tension in place so the whole thing can be seen at once. The method works because it makes the freeze tolerable. The freeze is what generates the insight; the method just keeps you there long enough for the insight to arrive.
Reading adversarial behaviour
This also opens a more compassionate way to read adversarial behaviour, in yourself and in others. When someone reaches for opposition, the first question is no longer what's wrong with them? The first question is what is too much for this system to hold right now? The adversarial stance is not always malice. Often, it is an honest signal that the system is at its limit. That doesn't excuse the behaviour. But it tells you something about the intervention. A system at its limit doesn't need more argument. It needs more capacity.
That is what the cloud builds. Not a clever solution. Not a better compromise. The capacity to hold the complexity that the conflict was throwing away.
From method to second nature
The first times you use the cloud, it is unambiguously System 2 work. Slow. Deliberate. Effortful. That is the point — the method is designed to force the slower system online when System 1 would otherwise close the space.
But the cloud is not where you stay. It is a bridge between System 1 and System 2. Each time you walk it, the path becomes more familiar. What started as deliberate scrutiny becomes recognition. What started as recognition becomes anticipation. Eventually, the way of holding complexity that the cloud taught you stops requiring the formal ten steps at all. It becomes how you see. It becomes how you respond. It becomes second nature — what is often called unconscious competence.
This matters more than it might sound. Inertia gets its grip from being the only fast answer in the room. When the practised pattern lives in System 1 alongside the old one, there are two fast answers available — and the new one has been shaped by everything the cloud surfaced. The contest is no longer between an expensive practice and a cheap habit. It is between two habits, and the practised one wins more often than not.
Breakthrough Principle: The cloud is a bridge between System 1 and System 2. Initially, it requires deliberate System 2 effort. With practice, it becomes second nature — unconscious competence — and the grip of inertia significantly loosens.
Sources for this appendix
- Kahneman, D. (2011). Thinking, Fast and Slow. — the source of the System 1 and System 2 framing, developed over decades of collaborative research with Amos Tversky.
- Frankl, V. E. (1946). Man's Search for Meaning. — the source of the space between stimulus and response.
See Sources & Further Reading for full entries.