Chapter 15: The Way You Think

David's second cloud was not about delegation.

It arrived three weeks into his daily practice, on a Sunday evening. He was sitting with his wife, half-watching something on television, and she said something about a holiday they had been talking about for months. He heard himself say, "We'll see." She went quiet. He went quiet. The evening moved on.

Later, lying awake, he recognised the shape. The pull between two things he wanted. The compromise that satisfied neither. The pattern repeating.

"I know what this is," he said in our next session. "It's a cloud. It's not a work cloud. But it's the same structure."

He was right. And the fact that he could see it — without prompting, without a facilitator, without the book open in front of him — was the point.

Sarah's second cloud

Sarah's arrived at work, but not in the leadership meeting.

Her direct report, Priya, had been underperforming for weeks. Sarah knew she needed to have the conversation. She also knew she had been avoiding it — and she knew why she had been avoiding it, because she could feel the same structure that had kept her quiet in the boardroom now keeping her quiet with her own team member.

Different room. Different stakes. Same architecture.

She sat down one evening with a blank page and built the cloud from scratch. D′ — I cover for Priya — absorbing what she drops, redistributing to the team, filling the gaps myself. D — I stop covering for her. She worked through the benefits, the assumptions, the UDEs. By the time she reached the A→C arrow, she could see the Big Assumption without needing to search for it: If I hold Priya accountable directly, I will damage the relationship permanently.

She had met that assumption before. It was wearing different clothes, but it was the same one that had kept her silent in the leadership meeting for three years.

"The cloud didn't just help me have the conversation," she said afterwards. "It showed me that the conversation and the boardroom were the same pattern. Once I could see that, both of them got easier."

The second cloud changes everything

Your first cloud is a revelation. You see the structure of a conflict that has been running your life, and you dissolve it. That is powerful, and for many people it is enough to justify the work.

Your second cloud is something else entirely.

The third or fourth cloud is where the method stops being a tool you use and starts becoming the way you think. Not because you have memorised the steps — that takes time and practice — but because you have begun to see differently. Conflicts that used to feel like immovable facts of life now reveal themselves as structures with assumptions inside them. Problems that used to produce anxiety now produce curiosity. The question shifts from "How do I cope with this?" to "What's the cloud here?"

David built four clouds in the three months after his first one. The holiday conversation with his wife. A recurring tension with a board member about risk appetite. His own relationship with exercise, which he had been meaning to address for years. A strategic disagreement with his CFO about capital allocation.

Not all of them dissolved as cleanly as the first. The board member cloud took two attempts to get the A→C assumption right. The exercise cloud surprised him — the Big Assumption underneath it turned out to be connected to the same identity question his delegation cloud had surfaced. The CFO cloud led to a conversation that changed the relationship.

Sarah built three. The conversation with Priya. A long-standing tension with her sister about their mother's care. And — the one that surprised her most — a cloud about her own ambition, which she had been quietly suppressing since the day she was promoted.

Each cloud was faster than the last. Not because they were easier — some were harder — but because the method had become familiar. The steps were no longer something she looked up. They were something she did.

The operating system

There is a moment, somewhere around the seventh or eighth cloud, where something shifts that is difficult to describe but unmistakable when it happens.

You stop using the Evaporating Cloud. You start thinking in clouds.

The formal ten-step process is still there. You can’t teach it, facilitate it, or walk someone else through it yet, but for you, the process has compressed into something faster and more intuitive. You notice a conflict forming — in a meeting, in a relationship, in your own head — and before you have consciously decided to build a cloud, you are already asking: What's the D′? What's it protecting? What assumption is holding this in place?

This is not a technique any more. It is becoming an operating system.

And an operating system brings its own confidence. Not the confidence of someone who has memorised answers, but the confidence of someone who knows they can find the structure inside any problem. You stop fearing conflict — not because you enjoy it, but because you know what to do with it. You stop avoiding difficult conversations — not because they have become easy, but because you can see what is underneath them. You stop feeling stuck — not because life has become simpler, but because stuckness now has a shape, and shapes can be worked with.

David said it plainly: "I used to dread the problems I couldn't see a way through. Now I'm curious about them. That's the biggest change — not any single cloud, but the fact that I'm not afraid of the next one."

Sarah said it differently: "I think in structures now. When someone describes a problem, I can see the cloud before they've finished talking. Not because I'm clever — because the method trained me to see it."

Both of them are describing the same thing. The Perry Approach, practised beyond a single cloud, does not just solve the problem you brought to it. It changes the way you think about all problems. It becomes the lens through which conflict stops being a threat and starts being a signal — a signal that assumptions are present, that structure exists, and that something better is available on the other side.

Goldratt's mission

Eliyahu Goldratt spent his life trying to help the world think.

That sentence sounds grandiose until you understand what he meant by it. He did not mean thinking as an academic exercise. He did not mean critical thinking as a curriculum subject. He meant the practical, daily, life-changing capacity to look at a situation that feels impossible and find the assumption that is making it feel that way.

In my view the Theory of Constraints — the body of work from which the Evaporating Cloud emerged — was never really about manufacturing, or supply chains, or project management, though it transformed all of those. It was about the way human beings get stuck. We get stuck because we accept constraints as facts when they are actually assumptions. We get stuck because we treat conflicts as trade-offs when they are actually structures waiting to be dissolved. We get stuck because no one taught us to see the logic underneath our own behaviour.

Goldratt built the tools — the Evaporating Cloud among them — each a different way of making invisible thinking visible, so that it could be examined and, where necessary, changed.

The Perry Approach stands on those shoulders. It takes one of Goldratt's most powerful tools — the Evaporating Cloud — and extends it into the territory he always believed it could reach: the inner conflicts that shape how leaders lead, how teams work, how organisations transform, and how people grow.

I consider it an honour and a privilege to carry that purpose forward.

What this book has given you

You have learned to see conflict as structure, not as failure.

You have built a cloud — your cloud — and traced the logic that holds your current pattern in place. You have surfaced the assumptions on both arrows, found the bigger C that transcends the trade-off, and written the evolved belief that lets the new pattern sustain.

You have a unified solution and a daily practice. You have the four rhythms, the NOT, and the evidence journal. You have everything you need to dissolve the cloud you brought to this book.

But the real gift is not the first cloud. It is what happens after.

When you build your second cloud, and your third, and your fourth, the method stops being something you do and becomes something you are. The way you see problems changes. The way you hold conflict changes. The confidence that comes from knowing you can find the structure inside any problem — that confidence changes everything else.

Your part

If this book has helped you see something you could not see before — if the cloud gave you a way through a conflict you had been living with — then I have one request.

Share it.

Not because I need readers, though I welcome them. Because every person who learns to see conflict as structure rather than threat makes the world a little less stuck. Every leader who stops avoiding and starts dissolving makes their organisation a little more capable of the conversations it needs to have. Every person who builds a cloud with someone they care about — a colleague, a partner, a friend — extends the reach of this work in a way no book can do alone.

The cloud begins again

Every situation can be substantially improved; even the sky is not the limit. — Eliyahu M. Goldratt, The Choice

There is one last thing to see, and it is the thing that turns a method into a way of living.

When you dissolved your cloud, you did not do it down at the surface, where the two courses of action pull against each other — D′ and D, the place where the conflict feels loudest. That is where most people try, and it is why most people end up with a compromise that satisfies neither side. You worked higher up, on the assumptions holding the conflict in place: the belief that the need you were protecting could only ever be met by that one action — the C→D′ arrow — and the deeper belief about what your real goal required — the A→C arrow. That is where a conflict actually dissolves — not by choosing between the two actions, but by enlarging the need beneath them. The need you were protecting grew — your C — until it was large enough to hold both what you were guarding and what you were reaching for: your C and your B, together, in a single need that no longer had to choose. That is transcendence. Not balance, not trade-off — a bigger container that holds both.

But here is what happens next, and it is easy to miss.

Once you live the unified solution — once that enlarged need is no longer an idea on a page but simply the way things now are — it no longer sits comfortably beneath the goal you began with. That goal — the objective at the very top of the cloud, A — was sized for the old conflict. The larger need presses upward, and the objective itself begins to expand to make room for it. Your sense of what you are really trying to achieve grows. And the moment that objective expands — the moment A grows — a new cloud comes into view: one you could not have seen before, because you were not yet standing high enough to see it.

This is why the method does not end. It returns.

You arrive back at Step 1 — What's really happening here? What's the D′? — but you are not where you began. You are on a wider orbit. The conflict you can now see only became reachable because you dissolved the last one. Each cloud expands the need; each enlarged need expands the objective; each expanded objective reveals the next cloud. It is not a loop that carries you back to the same place. It is a spiral that keeps widening.

I have come to think of it as something like the big bang theory — an ever-expanding universe. A single point of tension — one cloud, fully dissolved — and the whole frame expands outward from it, and goes on expanding, for as long as you keep returning to Step 1 with the courage to look.

Think of where this began. David's first cloud was about delegation — about whether he could ever let go enough to lead. A year on, he had built more than he could easily count, and he had his answer: he got the CEO role. The conflict he was working on by then was one he could not even have named when we started. Sarah's first cloud kept her silent in a boardroom for three years; the cloud that surprised her most — about her own ambition — turned out to be a doorway rather than a destination, opening a question she is still living inside. Neither of them is finished. That is not the method falling short; it is the method doing exactly what it is built to do. Every cloud they dissolve uncovers the next.

So this is my invitation, and it is where I will leave you. Close the book. Notice how far the universe of what you thought was possible has already grown. Then find your next cloud — and begin again at Step 1.