Chapter 1: Why Conflict is Your Secret Weapon

The Executive Who Couldn't Stop Working Late

"I know I should delegate more, but..." David's voice trailed off as he sat across from me in his corner office, the London skyline darkening behind him. It was 7.30pm, and once again, he was the last one in the building.

As Chief Operations Officer of a major airline, David was brilliant, driven, and utterly exhausted. His team respected him, his board valued him, but his family barely saw him. He'd hired me to help with "time management," but we both knew it went deeper than that.

"Let's start with the obvious," I said. "You want to delegate more. What would that give you?"

David leaned forward. "Time. Headspace. I've got people on my team who are ready for more — I can see it. If I let go properly, they'd develop faster. The whole operation would be more resilient. It wouldn't all depend on me being in the room."

"That sounds good. What else?"

"My family." His voice softened. "My daughter asked me last week why I never make it to her concerts. I didn't have an answer. If I could delegate properly, I'd have evenings back. I'd be a better father. A better husband. Probably a better leader, honestly."

He meant every word. This wasn't someone who didn't understand the benefit of letting go. He could see it clearly. He wanted it.

"So you can see everything delegating would give you," I said. "And it sounds like you've really tried."

"Dozens of times."

"Then, what happens?"

"I start to hand something off. I brief them, I set it up properly. And then..." He paused. "Then I start thinking about all the ways it could go wrong. The mistakes that could be made, the delays to on-time performance. The board paper that wouldn't be tight enough — the budget blow-out. So I say, 'Actually, I'll just handle this one myself.' Every time."

I let that land for a moment.

"David, listen to what you just described. You didn't say you struggle with delegation. You said you set it up properly, you brief your people, you get everything ready — and then you take it back. Every time."

He opened his mouth to respond, then stopped.

"That's not a delegation problem. Delegation is something you're perfectly capable of doing — you just told me you do it well. What you're actually describing is a pattern of handling everything yourself. That's a different thing entirely."

David sat with that for a long moment. "I suppose I've always framed it as 'I need to delegate better.' But that's not really what's happening, is it? I delegate fine. I just... undo it."

"Exactly. So let's look at what's actually happening, not what you walked in thinking was happening. When you handle everything yourself — what does that give you?"

"Quality decisions. More control. Better performance. When I do it myself, I know it's done right."

"So there's something valuable for you in handling everything yourself."

David looked at me sharply. He hadn't expected that.

"Think about it," I said. "Handling everything yourself isn't just a bad habit. It's giving you something you need. Confidence that the standard is met. Certainty that your name is attached to work you can stand behind. Meeting your own performance targets."

He nodded slowly. "I suppose that's right. It's not just control for control's sake. It's... I just need to know it is getting done right."

"That makes sense. What else do you think it gives you?"

David started to open up. “I maintain my credibility. More success. More opportunity.”

“And why is that important to you?”

A long pause. Then, quietly: "I suppose... it makes me important. It proves I’m good at what I do. It will make me the preferred candidate for the next Group CEO role I know is coming up."

There it was — not as a confession, but as a discovery. David wasn't failing to delegate. He was succeeding at protecting something that genuinely mattered to him. Two legitimate needs, both real, both valuable — pulling him in opposite directions.

David wasn't struggling with delegation. He was at war with himself. And both sides of that internal war had a point.

The Hidden War Within

If you're reading this book, you're probably fighting your own internal war. Not the dramatic, visible kind — the quiet, exhausting kind that plays out in a thousand daily decisions:

• The part of you that wants to speak up in meetings versus the part that fears looking foolish
• The drive for career advancement battling against the desire for work-life balance
• The need to be authentic fighting with the pressure to fit in with others
• The ambition to lead change while wrestling with the comfort of staying with the status quo
• You might even be like David, needing to keep control and needing to let go at the same time

Right now, you're probably thinking about your own internal conflicts. The ones that keep you up at night. The ones that make you feel like two people trapped in one body. The ones you've tried to solve a dozen different ways. If you are not thinking about them, then, I invite you to. This is your opportunity.

These conflicts aren't character flaws or personality traits. They're internal conflicts, and they're costing you more than you realise.

The Personal Price of Internal Conflict

When you're constantly fighting yourself, everyone loses:

You lose energy: Internal conflicts are exhausting. You spend more energy debating yourself than doing the work. By 3pm, you're drained from the constant internal wrestling — fighting that imposter feeling.

You lose clarity: When part of you wants one thing and part wants another, decisions become agony. You second-guess yourself, change direction midstream, and wonder why you can't just "get it together."

You lose authenticity: You present different versions of yourself depending on which internal voice is winning. Colleagues sense the inconsistency. They pull back, unsure which version of you they're getting today.

You lose opportunity: While you're stuck in internal debate, opportunities pass by. That promotion, that project, that moment to make a real difference — gone while you were paralysed by competing needs.

The Ripple Effect

But here's what makes it worse: internal conflicts don't stay internal.

What was happening around David wasn't a David problem. It is what happens around every leader carrying an unaddressed conflict — which is to say, around all of us. None of this is malice. None of it is incompetence. It is the perfectly logical operation of a human system designed to protect something that genuinely matters. We all run some version of it. We all send some version of the cost into the system around us.

His direct reports stopped developing. David had talented people — people he'd personally recruited because he recognised their potential. But every time he pulled a project back, every time he said "Actually, I'll handle this one," he sent the same message: I don't trust you to get this right.

He didn't mean that. He would have been horrified to hear it described that way. But that's what his team received.

Over time, his best people stopped reaching for more. Why would you stretch for responsibility that's only going to be taken away?

High performers left. The ones with the most ambition and capability — exactly the people David needed — were the first to go. They left for roles where someone would actually let them lead.

David told himself it was the market, the competition, the salary packages. It wasn't. Exit interviews told a consistent story: I couldn't develop here. There was no room for my expertise.

The remaining team learned dependency. Those who stayed adapted to the system David had inadvertently created. If the COO was going to review everything anyway, why invest the extra effort in getting it perfect? If he was going to rewrite the board paper regardless, why agonise over the first draft?

David's need for control trained his team to bring him problems instead of solutions, drafts instead of finished work, questions instead of decisions.

He was creating the very incompetence he feared.

His exhaustion changed every interaction. By mid-afternoon, David was running on fumes — not from productive work, but from carrying the cognitive load of an entire operation on his own shoulders. His patience shortened. His feedback became curt.

People learned to avoid him after 3pm, which meant decisions stalled, which meant more work backed up for the following morning, which meant he arrived earlier, stayed later, and grew more exhausted still.

The culture took on his conflict. This is where the ripple becomes a wave. David's internal conflict — the war between letting go and holding on — didn't just shape his behaviour. It shaped the organisational culture around him.

His department became risk-averse, because he modelled risk-aversion. It became hierarchical, because every meaningful decision flowed through one person. It became reactive rather than strategic, because David was so deep in operational detail that he had no capacity left for the forward-looking work his role actually demanded.

And the cycle fed itself. The more his team underperformed, because he'd trained them to, the more evidence David had that he couldn't delegate. See? When I hand things off, they don't meet the standard.

Every failure confirmed his belief. Every confirmation drove him deeper into the pattern.

The conflict wasn't just persisting. It was strengthening itself with every revolution.

David is not the only source of the cost. He is one location of it.

The same pattern is playing out around every other leader in the building at the same time — each one carrying their own version of an unaddressed conflict, each one protecting something that genuinely matters, each one inadvertently shaping the system around them. The costs don't sit in any one office. They compound — leader by leader, team by team, department by department, decision by decision — until they become indistinguishable from the culture itself.

Your Conflict Contains Intelligence

"David," I said, "what if your need for quality performance and maintaining credibility isn't a weakness to be fixed? What if it's intelligence trying to emerge?"

He looked sceptical. "Intelligence? It's destroying my life."

"Exactly. When someone as smart as you does something this destructive, repeatedly, despite knowing better... that's not stupidity. That's your system protecting something important."

Conflict is not proof that something is wrong. It is proof that something important is competing.

Why Our System Reaches for Conflict

There is a question hiding underneath everything you've read so far. If conflict is exhausting, costly, and self-reinforcing — why does it keep happening?

The answer is uncomfortable until it isn't.

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.

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.

This is why pushing harder — or walking away faster — rarely changes anything. You're not addressing the underlying tension; you're adding load to a system that was already at its limit. The harder you fight, the more the system needs the adversarial frame to keep functioning. The harder you avoid, the more the system needs the distance. The conflict isn't there because the other person disagrees with you, or because they won't engage. The conflict is there because there isn't room — in them, in you, in the situation — to hold what would be required to genuinely integrate.

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'll 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'll 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.

This is what was happening to David. He wasn't a person who couldn't delegate. He was a person whose system was at capacity — full of the responsibility, the standard, the visibility, the stakes — reaching for the lowest-cost answer available. I'll just do it myself. The take-back wasn't really a fight response or a flight response — it was an escape from the freeze, from the unbearable suspension between briefing his people and trusting them. The pattern wasn't I can't delegate. It was I can't stay in the space long enough for something new to emerge. That move kept the system running. It also kept the conflict in place, because nothing had been integrated.

What changed for David wasn't willpower. It was structure. The cloud gave his system a way to hold both legitimate needs at once — confidence in the standard and development of the team — without throwing either away. The capacity to hold both was what made the breakthrough possible.

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.

In practice, the shift is small in words and large in everything else. Instead of you and me against each other because of the problem, it becomes you and me against the problem. The opposition hasn't disappeared. It has been relocated — onto the thing that was overloading both systems in the first place. That is what the cloud does.

One more thing about System 1 and System 2 before we move on.

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.

The Architecture of Internal Conflict

Through my work with hundreds of leaders and their teams, I've discovered that internal conflicts follow a predictable pattern:

1. You want two seemingly incompatible things: Success AND balance. Control AND collaboration. Security AND satisfaction. Current state AND future state.
2. Both desires are legitimate: Each serves a real need, protects something valuable, or honours a deep commitment.
3. Traditional thinking says choose: Pick one. Compromise. Find the middle ground. Be "realistic."
4. So you oscillate: Monday you're all about delegation. By Wednesday you're taking everything back. You cycle, feeling inconsistent and weak.
5. The conflict persists: Because both needs remain valid. Choosing one doesn't make the other disappear.

Steps 4 and 5 have a name. The cycling, the pull back into the same pattern despite genuine effort — this is your own inertia. Not laziness. Not lack of discipline. Inertia is the weight of a system that has been running for a long time, protecting something it believes you cannot do without. It is a structural feature, not a moral failing. You do not dismantle it through effort. You dismantle it by showing the system there is another way to honour what it has been protecting.

You don’t have to stay stuck.

Where Performance Actually Lives

Every workplace runs on two types of resources.

The first is physical. Raw materials, buildings, machinery, vehicles, technology, money in the bank. These are the assets that appear on the balance sheet. They can be counted, valued, insured, and depreciated. When most people picture an organisation, this is what they picture.

The second is people.

And here is the part that's easy to miss: the physical resources, on their own, are inert. A factory full of machines produces nothing. A warehouse of raw materials sits still. Money in a bank account earns interest but creates no value. Until something animates them, they are cost without return.

What animates them is rules. Rules, policies, beliefs, and behaviours that determine how the physical resources are used — when they're switched on, what they produce, in what sequence, to what standard, for whom, at what pace, by whom, and to what end. Without rules, the machines stay off and the materials never move. With rules, an organisation produces. That's the whole game.

And the rules live inside the people.

This is why people aren't just another resource. They are a different kind of resource entirely — the carriers of the rule system that makes every other resource productive. Whatever an organisation achieves, it achieves because the people inside it are following a particular set of rules. Whatever it fails to achieve, it fails to achieve for the same reason.

The rules come in two forms.

The first is written. Policies. Procedures. SOPs. Role descriptions. Process maps. Decision rights. The org chart on the wall. This is the system most people mean when they talk about how an organisation works. It's documented, debated, audited, and, when something goes wrong, revised.

The second is unwritten. Nobody wrote it down. Nobody signed it off. There is no policy document in any drawer that says "we don't challenge the CEO in front of other directors" or "the standard isn't really met until I've personally checked it" or "you can leave at five if you've made it visible you didn't really want to." And yet every person in the building obeys these rules every day, often without noticing they're doing so.

The unwritten rules are where behaviour actually lives. Which means the unwritten rules are where performance is actually decided.

Eliyahu Goldratt — the originator of the Theory of Constraints — saw this himself. When describing his book, Isn't It Obvious?, he wrote:

"What I have tried to show in this book is that the formal system is not really the most important thing in the company. The informal system is even more strong in terms of what makes a company. The friendship, the relationships, the harmony, that is what makes the company into a big company or a small company."

The informal system is the unwritten rules. Goldratt named the territory. What he didn't finish was the method for working inside it. That is what the Perry Approach offers.

Almost every continuous improvement methodology you've encountered — lean, six sigma, agile, the textbook version of TOC, every transformation programme that's ever been sold to your organisation — operates on the written rules. They map processes, find bottlenecks in flow, redesign workflows, redraw role descriptions, rewrite policies. When the binding rule is written, these tools are excellent.

But the moment the binding rule is unwritten, every one of them goes quiet. They have no language for it. No tool for it. No method for surfacing it, let alone changing it. So they leave it alone — and the unwritten rule, the one no one ever wrote down, continues to govern what the physical resources do.

This is where the Perry Approach to the Evaporating Cloud earns its place.

The Evaporating Cloud, used the way you'll learn to use it in this book, is a method for working with the unwritten rules. For surfacing the rules nobody documented. For naming the beliefs that were never voted on. For testing the assumptions that were never spoken. And, when the moment is right, for dissolving the conflict those unwritten rules have been protecting.

David doesn't have a delegation problem. He has an unwritten rule — the standard isn't really met until I've personally checked it — that nobody ever told him to obey, and that he has obeyed for fifteen years anyway. That one unwritten rule is determining how every physical resource around him gets used: his team's hours, his own hours, the airline's capacity to scale, the board's confidence in succession. Until the rule is surfaced, none of that can change. After it is surfaced, all of it can.

That is the territory this book is about.

Introduction to the Perry Approach

The Perry Approach to the Evaporating Cloud is not another framework for forcing yourself to change. Not another system for "overcoming resistance." Instead, it is a methodology for discovering why the conflict exists — and transcending it entirely.

The Perry Approach isn't therapy. It's not coaching as you know it. It's certainly not another time management system. It's a systematic method for transforming internal conflicts into breakthrough insights — a journey from "I'm stuck" to "Of course — why didn't I see that before?"

The Perry Approach is built on a radical premise: Your conflict isn't the problem. Your conflict is the solution trying to emerge.

Beyond Traditional Solutions

Most approaches to internal conflict fall into familiar patterns:

Willpower-based solutions: "Just decide and stick with it." This works briefly, then collapses when the underlying needs reassert themselves.

Compromise-based solutions: "Do a bit of both." This satisfies neither need fully, leaving you perpetually dissatisfied.

Priority-based solutions: "Focus on what matters most." This requires repeatedly choosing one legitimate need over another, building resentment.

Balance-based solutions: "Find equilibrium." This assumes the conflict is structural rather than dissolvable, condemning you to constant management.

The Perry Approach offers something different: transcendence. Not choosing between options, but discovering the hidden third way that honours both needs simultaneously.

Three Modes of Thinking That Drive Transformation

The Perry Approach uses three modes of thinking — deduction, abduction, and induction — working together as a cycle. Each one does work the others can't do, and the transformation only holds when all three are in motion.

• Deduction is the mapping work that makes your operating system visible. When you build a cloud, you use necessity logic to surface what has been running on autopilot. This is where the method begins — you can't change what you can't see.
• Abduction is the generative leap that produces a genuinely new possibility. This is where breakthrough lives — the moment you realise an assumption you have been treating as a fact is actually just a belief that can be challenged.
• Induction is the pattern-making that turns insight into new behaviour. It is how the operating system that runs your behaviour got built in the first place — and it is how the new pattern replaces the old one through deliberate practice.

The cycle is deduction → abduction → induction → deduction.

The conflict you are in runs on an old induction — a pattern that was once useful but has outlived its purpose. The Evaporating Cloud makes that pattern visible (deduction), opens space for a new possibility (abduction), and then practises the new possibility until it becomes the way you actually operate (induction). And because life keeps moving, the cycle begins again.

David's breakthrough followed exactly this path. Mapping the cloud made the underlying assumption visible — if I want confidence in quality, I must control it myself.

A new possibility then emerged — confidence doesn't require my control; it requires their capability.

Three months of disciplined practice turned that insight into a new way of leading.

This is also why willpower, technique-stacking, and "just decide" approaches don't last — they try to skip steps in a cycle that has to be worked through in sequence.

The David Breakthrough

David's breakthrough came when we mapped his conflict using the Evaporating Cloud Method. On one side: his need for quality and control. On the other: his team's need for development and autonomy. Both legitimate. Both important.

The traditional solution was compromise: delegate some things, keep others. This left everyone frustrated.

The Perry Approach revealed something different. David's need for "control" was actually a need for confidence that standards would be met. His team's need for "autonomy" was actually a need for development through meaningful responsibility.

The breakthrough: What if David's role was to build the capability in others that gave him confidence in them?

Within three months, David had created a development system where team members progressively demonstrated competence before taking on more responsibility. He had the confidence he needed. They had the growth they needed. No compromise required.

David now leaves at 5.30pm most days. His team's performance has improved. His family has him back. And he's no longer at war with himself.

It turned out that the part of him that wanted control and the part that wanted freedom weren't enemies — they were dance partners waiting for the right music.

But here's what matters most for you: David's breakthrough didn't come from my expertise. It came from the process. I asked questions. The cloud revealed what was hidden. David did the thinking.

The Perry Approach to the Evaporating Cloud Method is a process you can learn. Once you can build a cloud, you can sit with your own conflict and coach yourself through it — surfacing assumptions you didn't know you were carrying, discovering possibilities you couldn't see before. You don't need someone else to tell you the answer. The answer is already in your conflict. You just need a reliable way to find it.

Your Secret Weapon Awaits

Here's what David discovered — and what you're about to discover: The very conflict that's been exhausting you contains the seeds of your breakthrough.

Your internal war isn't a flaw to be fixed. It's intelligence waiting to be decoded. The Perry Approach gives you the tools to do exactly that.

A cloud persists only as long as you are defending it. The energy that holds it in place is the energy you spend protecting one side against the other. The moment you see the assumption underneath — the moment the system understands there is another way to honour both needs — the cloud dissolves. It evaporates. Not because you forced it to. Because it no longer has anything to do.

What if that conflict you've been fighting is your secret weapon? What if it is your new source of energy?

What You'll Discover in This Book

You'll learn to:

✅ Map your conflicts with precision, revealing their hidden structure

✅ Identify the legitimate needs on both sides of any internal struggle

✅ Surface the assumptions that make the conflict seem necessary

✅ Generate breakthrough solutions that transcend either/or thinking

✅ Implement sustainable change through both technical and adaptive solutions

Your Transformation Starts Now

You've been at war with yourself long enough. The exhaustion, the oscillation, the sense that you should be past this by now — all of it can transform.

Not through willpower. Not through compromise. But through understanding the intelligence your conflict contains.

By the time you finish this book, you'll understand why that conflict exists, what intelligence it contains, and how to transform it into your competitive advantage. The war within is about to become your path to breakthrough.

Remember my invitation to think about your conflict. I invite you to think about it again.

Then, turn the page. Let's decode what your conflict is trying to tell you.

Chapter Reflection

Before moving to Chapter 2, take a moment to reflect:

1. What internal conflict do you find yourself cycling through repeatedly?
2. What competing needs might both sides be trying to protect?
3. How is this internal conflict affecting your leadership and relationships?

Write your answers in a workbook or journal. In Chapter 2, you'll discover why traditional approaches to these conflicts often make them worse — and what actually works instead.

What's Next

In Chapter 2, you'll discover where the Perry Approach came from — the convergent insights from constraint theory and developmental psychology that shaped the methodology you're about to learn. Everything you need is in this book. You can work through it on your own, at your own pace.

Support for this page

Recognising the war within — seeing that both sides of your conflict are legitimate and that the pattern contains intelligence — is the step that changes everything that follows. Most people read this chapter and feel the recognition. Fewer know what to do with it.

The Rising Above the Clouds - The Course opens this chapter up into a conversation. It gives you the opportunity to discuss the ideas directly with Karl through the author discussion tab, and to chat with RIC — the Rapid Improvement Coach, an AI agent trained on the Perry Approach who can offer deeper insights into the method. RIC helps you name the conflict you recognised as you read and holds the early shape of it with you — beginning the work of seeing both sides as intelligent rather than one side as the problem. You set the pace; RIC stays with the recognition and does not rush you toward solutions. The course also includes membership of the Conflict Club.

Rising Above the Clouds — The Course