Chapter 3: A TRIP Through the Cloud

Meet Sarah

Sarah sits across from me, coffee growing cold between us. She leads Customer Experience at a logistics company—smart, capable, respected by her team. But something's wrong.

"I know what I need to do," she says. "I've known for months. I need to speak up in leadership meetings. Challenge the decisions that don't make sense. Push back when targets are unrealistic."

She pauses, stares at her cup.

"But I don't. Every time. I sit there, I see the problems, I know what I should say… and I say nothing. Then I spend the next week cleaning up messes that could have been avoided."

I've heard variations of this story hundreds of times. The specifics change—the industry, the stakes, the characters—but the pattern is always the same. Someone who knows exactly what they should do. And can't do it.

You met David in Chapter 1. His pattern was the fight shape of this same trap — aggressive in its defence. Every task pulled back. Every weight carried himself. Sarah's pattern is the opposite shape. It is flight — passive in its defence. Withdrawal from the moment of contribution. The weight quietly left in the hallway.

Same System 1 response to a system at its limit. Different exit. The Evaporating Cloud is not a method for one type of person — it is a method for the underlying structure that produces both. Watching Sarah work through her cloud, you are watching the same method that dissolved David's, applied from the opposite side.

This is the understanding-action gap in action. And it's exactly the kind of conflict The Rapid Improvement Process — TRIP™ — is built to dissolve.

The Method Overview

“If I had an hour to solve a problem, I'd spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.” — Often attributed to Albert Einstein

A TRIP takes this to heart. Nine of its ten steps are spent understanding and reframing the conflict; by the time we reach the solution, it has almost built itself.

Before we walk through Sarah's cloud, here is the shape of what you're about to watch. You met the TRIP at the end of Chapter 2: Development of The Rapid Improvement Process: one live conflict, taken through all ten steps of the Perry Approach to the Evaporating Cloud in a single focused sitting. The Perry Approach supplies the method and its rigour; a TRIP runs it end to end on a real conflict, with an outcome the person keeps.

Sarah's is a TRIP at its first level: one stakeholder, one cloud, worked one-to-one across a couple of hours in a café. The same ten steps hold when two parties sit across a table, or a whole team is in the room. What changes is how many logics have to be held at once. That is the trip through the cloud the chapter title promises.

In this chapter you'll watch a whole TRIP from start to finish, so you can see how the pieces fit together. The chapters that follow slow each step down—the nuances, the common pitfalls, and what mastery actually looks like in practice.

As we covered in Chapter 2, each phase draws on a different mode of thinking: deductive reasoning maps the conflict structure, abductive thinking generates breakthrough possibilities, and inductive practice builds lasting change.

A TRIP moves through three phases:

Phase 1: Building the Cloud (Steps 1–7, Chapters 4–10)

We map the conflict — identifying current state, future state, the benefits of each, and the unified outcome. Then we read the cloud back to verify the logical structure holds, and surface the undesirable effects the conflict is creating — the Conflict Tax, the real cost that makes it worth solving. This gives us a clear picture of what's actually happening and why it matters.

Phase 2: Evaporating the Cloud (Steps 8–9, Chapters 11–12)

We challenge the assumptions holding the conflict in place. First, we generate alternative ways to protect what the current behaviour gives you. Then we surface the deeper belief that keeps you locked in, and find a bigger belief that can hold both sides. This is where breakthroughs happen.

Phase 3: Creating the Solution (Step 10, Chapter 13)

We combine the new adaptive belief with the relevant technical options — ordered by prerequisite for fastest implementation — to form a coherent way forward, and name the first actions that set it moving.

Reading the Cloud

In Chapter 2 we introduced the Evaporating Cloud diagram — five boxes connected by arrows. Here's a reminder of how to read it — and don't let the letters put you off. Each one is simply shorthand for a plain idea, and I'll name that idea in full every time it appears. You say D′ as "D-prime": it shares its letter with the future state D because both are actions — things you do — with the prime marking the one you're doing now. A, B, and C are the shared goal and the two sets of benefits beneath it.

In the Perry Approach, D′ (the current state — what you're actually doing) sits at the bottom right, with C (the benefits your current state is protecting) to its left.

D (the future state — not D′) sits at the top right, with B (the benefits the future state would give you) to its left.

A (the unified outcome) sits on the far left — the overarching goal that both paths serve. The arrows show logical necessity:

A requires both B and C; B requires D; C requires D′. The red conflict arrows between D and D′ show the tension at the heart of the cloud — you can't do both at the same time.

Keep this structure in mind as we work through Sarah's cloud. You'll see each position filled in turn.

Let's watch how this unfolds with Sarah.

Phase 1: Building Sarah's Cloud

Back in the Room

We're in a quiet corner of a café—the kind with good light and enough ambient noise that our conversation won't be overheard. Sarah has chosen the seat facing the wall. I notice this. She's already protecting herself, even in where she sits.

Her coffee sits between us, barely touched and going cold. She's been talking for fifteen minutes—circling the problem, explaining the context, justifying why it matters. I recognise this pattern. She's building the case for why this conflict is worth solving, as if she needs permission to work on it.

I let her finish, then pull out a blank sheet of paper.

"Sarah," I say, "everything you've told me makes sense. You know what the problem is. You know what it's costing you. What we're going to do now is map the conflict—not just describe it, but see its actual structure. The logic that's keeping it in place."

She nods, but I can see the scepticism. She's tried to solve this before. Therapy. Books. Positive affirmations. Nothing has stuck.

"This won't feel like a normal coaching conversation," I continue. "I'm going to ask you questions that might seem odd. I need specific answers—not general ones. The precision matters. Trust the process, even when it feels strange."

"Okay," she says quietly.

I draw a simple structure on the paper—five empty boxes waiting to be filled. Sarah looks at it like it's a puzzle she's not sure she can solve.

"We'll take it one step at a time," I say. "Let's start with what's actually happening right now. Not what should be happening. What is."

She takes a breath. We begin.

Step 1: Identify the Current State (D′)

"Sarah, let's start with what you're actually doing. Not what you should do. What do you do in these meetings?"

She shifts in her seat. "Well, I go in prepared. I have notes. I know what I want to say."

"And then?"

"And then..." she pauses, looking down at her coffee cup. "I sit there. I listen to people talk. I watch bad decisions get made. I have this whole script in my head of what I should say, and I... don't say it."

"What do you do instead?"

"I nod. I stay quiet. Sometimes if someone else raises a concern—I'll support their point. Add evidence. But I never introduce my own concerns. I never challenge."

There's a flatness in her voice. This isn't confession—it's resignation. She's described this pattern so many times it's become a fact about herself rather than a behaviour she's doing.

"So in those meetings, the behaviour you're actually doing is..."

"Staying quiet," she says. "I stay quiet."

I write it in the bottom box of the cloud structure: Stay quiet in leadership meetings to maintain harmony.

D′ (Current State): Stay quiet in leadership meetings to maintain harmony

She looks at the words on paper. "That's it? That's all we're starting with?"

"That's everything we're starting with," I say. "This isn't a judgement. It's not good or bad. It's simply what is. Where you are. And where you are makes sense—we just don't know why yet. That's what we're going to discover."

Sarah nods slowly, but I can see the scepticism. She expected analysis. Insight. Some explanation for why she's like this. Instead, we're just... naming what she already knows.

"We need to trust the process," I say again. "It builds."

Step 2: Articulate the Future State (D)

"Now," I say, "what's the opposite of staying quiet? What would you be doing instead?"

Sarah doesn't hesitate. "Speaking up. Being assertive. Finding my voice." The words come out like a well-rehearsed script.

"Hold on," I say. "We're not defining the solution yet. We're not even defining what 'good' looks like. We're just identifying the conflict. The tension. What you're pulled toward but can't seem to do."

She looks confused. "Isn't that what I just said?"

"You gave me a prescription. 'Being assertive.' 'Finding my voice.' Those are loaded with assumptions about what the solution should look like. Right now, all we need to know is: what's the alternative to staying quiet?"

"Not staying quiet," she says slowly.

"Exactly. Not D′. The absence or reduction of the current behaviour."

I write it in the box opposite to D′: Not stay quiet (Not D′).

D (Future State): Not stay quiet (Not D′)

Sarah frowns at the paper. "That seems... vague. Unhelpful even."

"It feels that way now," I agree. "But here's why it matters. If I let you define D as 'speak up confidently' or 'be assertive,' we've already decided what the solution looks like. We've closed down possibilities. But the specific how of D—the way you'll actually move beyond staying quiet—that emerges later, when we challenge the assumptions holding this conflict in place."

"So right now we're just establishing the conflict itself," she says.

"Exactly. You're stuck between D′ and D. Between staying quiet and not staying quiet. Between doing what you're doing now and doing something—we don't yet know what—different. That's the conflict. That's what we're mapping."

She looks at the two boxes on the page—D′ at the bottom, D opposite it. The space between them suddenly visible.

"I've been caught between these two things for months," she says quietly. "Years, maybe. I just never saw it this clearly."

"That's part of the Evaporating Cloud process," I say. "It makes the invisible visible. And once we can see the structure, we can work with it."

This feels abstract, but it matters. If we define D too specifically too early, we close down possibilities before we’ve understood the conflict. “Not D′” keeps the door open for whatever breakthrough emerges later.

Step 3: Surface the Benefits of the Future State (B)

Now we need to understand what not staying quiet would actually give Sarah. Not the abstract notion of "being heard" but the concrete benefits that matter to her.

"Sarah, imagine you're in one of those leadership meetings and you don’t stay quiet. You say what you see clearly and directly. What would that give you? What becomes possible?"

She pauses, considering. "Well, the problems would actually get addressed. Instead of watching a bad decision unfold and then spending the next week fixing it, we'd catch it early."

"What else?"

"My expertise would actually contribute. I've been doing this work for fifteen years—I know what works for our customers and what doesn't. Right now all that knowledge just sits unused while I watch preventable mistakes happen."

I can hear the frustration in her voice. This isn't abstract. These are real consequences she's living with.

"And for your team?"

Her face shifts. "They'd feel represented. Right now when customer concerns get dismissed or overlooked, my team knows I was in the room and said nothing. They're respectful about it, but I can see it. They need someone advocating for them at that level, and I'm not doing it."

"What would not staying quiet do for how senior leaders see you?"

"It would show I'm thinking strategically, not just managing the day-to-day customer experience. That I understand the bigger picture and can contribute to it. Right now I think they see me as competent at execution but not as a strategic voice."

"And for you personally?"

She sits with this one longer. When she speaks, her voice is quieter.

"I'd feel authentic. Like I'm actually showing up as the person I am, not performing some version of myself that keeps everyone comfortable. I'd feel aligned with my own values—integrity, honesty, speaking truth."

We capture what's emerged:

B (Benefits of Not Staying Quiet):

• Problems get addressed before they become crises
• Her expertise contributes to better decisions
• Her team feels represented and advocated for
• She demonstrates strategic thinking to senior leaders
• Customer issues get the attention they deserve
• She feels authentic and aligned with her values

These aren't wishes or aspirations. They're legitimate needs that aren't currently being met. They're part of what's calling Sarah toward change—the pull toward something better that she can clearly see but hasn't yet been able to reach.

Step 4: Surface the Benefits of the Current State (C)

This is where most approaches go wrong. They treat the current behaviour as a problem to be fixed rather than a solution that's working. We need to honour what staying quiet is giving Sarah.

"What does staying quiet give you? What would you lose if you suddenly started not staying quiet?"

Sarah's first answer is what just about everyone says to start with: "Nothing. It gives me nothing. It's just fear."

I wait.

"Well…" she continues slowly, "I suppose I don't make enemies. I stay safe. People don't see me as difficult or aggressive."

"What else?"

"I don't risk being wrong in front of everyone. I don't expose myself to criticism."

I keep probing. This is where the real work happens—getting past the surface justifications to the legitimate needs underneath.

"Tell me about those relationships with your peers. What does staying quiet preserve there?"

"Harmony, I suppose. We work together smoothly. There's no tension, no friction. We're a unified leadership team, at least on the surface."

"And with the senior leaders—the ones making the decisions you have concerns about. What are you preserving by staying quiet?"

She thinks about this carefully. "I'm... I'm allowing them to lead. I'm respecting their authority. When I stay quiet, I'm showing that I trust their judgment, that I'm not undermining them."

"Why does that matter to you?"

"Because they need to be able to lead confidently. If people at my level are constantly questioning them, it creates instability. And... honestly, I need them to trust me. To see me as someone who supports their leadership, not someone who makes their job harder."

This is the shift I'm listening for—from "not threatening" to the actual need being met. Sarah isn't simply avoiding being threatening. She's actively preserving something she values: the ability of leaders to lead, and her own position as someone trusted within that leadership structure.

"What else does staying quiet give you?"

"My reputation. People see me as collaborative, as a team player. That's not nothing—that's actually valuable. And..." she pauses, "emotional safety. Speaking up in those moments feels genuinely dangerous. Like I'm stepping into conflict, into confrontation. Staying quiet keeps me out of that danger zone."

Over twenty minutes of careful exploration, a rich picture emerges:

C (Benefits of Staying Quiet):

• Protection from being seen as aggressive or difficult
• Avoiding the risk of being publicly wrong
• Maintaining harmonious relationships with peers
• Respecting and supporting senior leaders' authority
• Preserving her reputation as collaborative and supportive
• Emotional safety from conflict and confrontation

These aren't weaknesses. They're legitimate needs. Sarah has built a successful career partly because she's collaborative, supportive, and respectful of leadership. Staying quiet isn't irrational—it's protecting something genuinely valuable.

Notice that B and C don't directly contradict each other. Sarah wants both—to be collaborative AND to contribute her perspective. To be safe AND to be authentic. The conflict isn't between B and C themselves. It's between how she's currently achieving them.

Step 5: Find the Unified Outcome (A)

"Sarah, if you could have all of B and all of C—full protection AND full contribution—what would that give you? What's the bigger thing both sets of benefits are serving?"

She thinks carefully. "I suppose… I want to be effective. Really effective. To make a difference in my role while building relationships that last."

A (Unified Outcome): Sustained effective impact in my leadership role

This is what Sarah is ultimately after. Both staying quiet (D′) and not staying quiet (D) are strategies aimed at this same goal. The tragedy is that her current approach—oscillating between them or defaulting to quiet—isn't giving her either. She's neither fully protected nor fully contributing.

Step 6: Read the Cloud

"Sarah, let's check the logic. I want to walk through each connection and have you tell me whether it makes sense."

We look at the Evaporating Cloud structure and test each arrow:

"First, A to B: To have sustained effective impact, do you need to contribute your perspective and have problems addressed?"

"Yes," she says. "Absolutely. I can't be truly effective if I'm not contributing."

"B to D: To contribute your perspective, do you want to NOT stay quiet in leadership meetings?"

"Well, yes. That's the obvious path."

"And A to C: To have sustained effective impact, do you also need to maintain relationships and stay protected?"

"Yes. If I damage relationships or make myself unsafe, my effectiveness won't be sustained."

"And C to D′: To stay protected and maintain relationships, you want to stay quiet in leadership meetings?"

She pauses. "That's what I've believed. Yes."

"Finally, D and D′: Can you stay quiet and not stay quiet at the same time?"

She smiles. "No. They're mutually exclusive."

"So the cloud is logically sound?"

"Yes," Sarah confirms. "This is exactly the conflict I'm living. Seeing it mapped out like this... it makes sense of what has been so confusing."

Step 7: Identify the Undesirable Effects

Now we need to understand what this conflict is actually costing Sarah. Theory of Constraints calls these Undesirable Effects (UDEs) — the negative consequences that make the conflict worth solving. Taken together, they are the Conflict Tax: what the conflict charges, week after week, for staying in place.

"Sarah, let's look at what this conflict is doing to you. What are the actual consequences of being stuck between staying quiet and not staying quiet?"

She thinks, then begins:

"Well, I'm exhausted. I spend so much mental energy in those meetings—monitoring myself, rehearsing what I could say, then beating myself up afterward for not saying it."

"What else?"

"I'm cleaning up messes that didn't need to happen. Bad decisions get made, I see them coming, and then I'm working late trying to fix them." She gives an example. "Last quarter we signed off a change to our delivery promise—narrowing the tracking updates customers receive, to cut cost. I knew from the complaint data exactly how customers would react. I was in the room, and I said nothing. My team spent months handling the fallout—the calls, the complaints, the customers we lost."

"And how does this affect you personally?"

Sarah's voice gets quieter. "I feel like an imposter. I'm senior leadership, but I'm not actually leading. I know I'm not showing up as the person they hired me to be."

We capture the UDEs:

Undesirable Effects of the Conflict:

• Constant mental exhaustion from self-monitoring and internal conflict
• Cleaning up preventable problems that drain time and energy
• Team frustration when operational realities aren't represented
• Missed opportunities for better decisions
• Growing sense of inauthenticity and imposter syndrome
• Diminishing confidence as the pattern repeats
• Risk of being seen as not contributing at senior level

These aren't abstract problems. They're the real price Sarah pays for this unresolved conflict. The UDEs make it clear why solving this matters—not just for Sarah's peace of mind, but for her effectiveness, her team, and the organisation.

Sarah looks at the list. The weight of it is visible on her face. Then she looks up.

"So how can I fix this?"

Her question tells me she's turned a corner. Not resignation. Not hopelessness. But genuine readiness to solve the problem now that she fully understands what it's costing her.

Now she can evaporate it.

Phase 2: Evaporating Sarah's Cloud

Most coaches would jump straight to advice at this point. Tell her what to do. Give her techniques. Assign her homework.

But that would miss the entire point of what we've just built. The cloud isn't just a map of the conflict—it's a map of the logic that maintains the conflict. And logic, when challenged properly, reveals its own weaknesses.

The cloud holds together because of assumptions. Hidden beliefs that seem so obvious we don't even question them. Sarah believes she must stay quiet to maintain relationships. She believes her effectiveness requires being liked. These aren't facts—they're assumptions. And every assumption can be tested.

This is where the Perry Approach differs most sharply from other methods. We don't try to overcome the conflict through willpower or positive thinking. We don't treat it as a problem requiring motivation or courage. Instead, we examine the logical structure that creates the conflict, identify the assumptions holding it in place, and systematically challenge those assumptions.

When you challenge an assumption properly, one of two things happens. Either you discover it's invalid—it was never true to begin with—or you discover it's too narrow. A belief that was once helpful has become too small to accommodate your current reality.

In Sarah's case, we're going to do both. First, we'll challenge the technical assumption—the belief that staying quiet is the only way to protect relationships. We'll generate alternative ways of achieving C (protection) without D′ (staying quiet). This gives Sarah options.

But options alone won't free her. The deeper constraint isn't technical—it's adaptive. It's the belief structure that makes staying quiet feel like the only safe choice. Until we challenge that deeper assumption, the technical options will feel like tricks or manipulations. Inauthentic.

So we'll go deeper. We'll surface the A-C assumption—the belief that connects her objective (effectiveness) to her need for protection. We'll make that unconscious belief conscious. And then we'll ask: what bigger belief could we hold?

This is transcendence. Not abandoning what matters, but expanding the belief structure to include more of what's true.

Here's how it went with Sarah.

Step 8: Challenge the C-D′ Assumption (Technical)

We start with the technical assumption—the arrow connecting C (protection) to D′ (staying quiet).

"Sarah, let's look at this connection between protection and staying quiet. The logic says: to have protection and maintain relationships, you must stay quiet. Let's test that. What would have to be true for staying quiet to be the only way to protect yourself and maintain relationships?"

She thinks, then begins listing the hidden assumptions:

"Well... I suppose I'm assuming that speaking up always creates conflict. That there's no way to raise concerns without it becoming confrontational."

"What else?"

"That people who challenge decisions are seen as aggressive. As difficult. That once you get that reputation, you can't shake it."

"Keep going."

"If I'm wrong publicly—if I speak up and I'm mistaken—I'll lose credibility permanently. People will remember that I was wrong, not all the times I was right."

She's on a roll now, surfacing beliefs she's held for so long they've become invisible.

"I think I'm assuming senior leaders don't actually want to hear dissent. That they're looking for support, not challenge. And that being quiet is the only way to be seen as collaborative and supportive."

I write these down so we can see them clearly. Assumptions often lose their power when we make them explicit.

"Now," I say, "here's the key question. These assumptions connect C—the protection and relationships you need—to D′—staying quiet. But what if we could get C a different way? What options exist to maintain protection and relationships while replacing staying quiet?"

Sarah looks uncertain. "I'm not sure I follow."

"You need protection. You need good relationships. Those are legitimate. But what if speaking up didn't automatically threaten them? What are different ways you could speak up—ways that might actually preserve the protection and relationships you value?"

"You mean... how could I speak up without it being threatening?"

"Exactly. And the answer will have something to do with B—with contributing your perspective effectively. Let's brainstorm. No filtering yet, just possibilities."

She's quiet for a moment, then begins tentatively.

"I suppose... I could frame things as questions rather than challenges? Like, 'Have we considered what happens if...' instead of 'This won't work because...'"

"Good. What else?"

"I could talk to people before the meeting. Build alliances. So when I raise a concern, it's not just me—it's a shared observation. That feels less risky somehow."

"Keep going."

Her pace picks up as possibilities emerge. "I could acknowledge what others are saying first. Show I understand their perspective before adding mine. That way I'm building on their thinking, not opposing it."

"What about timing?"

"Timing... yes. If I contribute early in the discussion, it's shaping the conversation. But if I wait until decisions are nearly made and then object, that feels like I'm trying to derail things. So early contribution might actually feel more collaborative."

"And how you frame the concern itself?"

"Focus on outcomes we all care about rather than problems. Connect my concern to what we're trying to achieve together—better decisions, operational success, whatever matters to everyone in the room."

"What about the substance of what you say?"

"Use data and evidence rather than just opinion. If I can say 'here's what happened last time we tried this' or 'here's the customer impact', that's different from 'I think this is a bad idea.' It's less about me and more about reality."

"And before you even walk into the room?"

"Prepare. Know my two or three key points before the meeting starts, so I'm not composing them under pressure. And start smaller—raise something lower-stakes first, rather than waiting for the biggest decision of the quarter to find my voice."

We capture what's emerged:

Technical Options to Maintain C While Replacing D′:

• Frame contributions as questions rather than direct challenges
• Build alliances before meetings so concerns are shared, not solo
• Acknowledge others' points before adding perspective
• Contribute early enough to shape, not late enough to derail
• Focus on shared outcomes rather than problems
• Use data and evidence rather than opinion
• Connect concerns to objectives everyone cares about
• Prepare key points before meetings
• Start with lower-stakes contributions to build the muscle

These are all technical solutions—different ways of speaking up that might preserve what staying quiet was protecting. Real possibilities. Concrete approaches Sarah could actually use.

But I notice something in her face. Even as she's generating these options, there's hesitation.

"Sarah, you've come up with some solid approaches here. Have you tried any of them before?"

She nods slowly. "Some of them. Yes. I've tried framing things as questions. I've tried the 'I'm building on your point' approach."

"And?"

"I still freeze. Or I try it once, it feels awkward and forced, and I never do it again. It's like... intellectually I know these techniques make sense. But in the moment, when I'm sitting in that meeting, none of it feels real. It feels like I'm manipulating. Like I'm using tricks to get away with something I shouldn't be doing."

And here is the real obstacle, surfacing at last. The techniques aren't the problem. The belief structure underneath is.

"That's because they are tricks—as long as you still believe your fundamental value comes from being agreeable. If speaking up is inherently threatening, then these are just clever ways to disguise that threat. They feel inauthentic because they contradict your core belief about how value and safety work."

Sarah sits with this. "So technical solutions alone won't fix this."

"Exactly. They're necessary—you'll need ways to speak up skilfully. But they're not sufficient. We need to go deeper."

This is why technique-only coaching so often fails: without an adaptive shift, technical options feel like manipulation.

Step 9: The Adaptive Shift — Surfacing the A-C Assumption

Now we explore the adaptive assumption—the arrow connecting A (sustained effectiveness) to C (protection).

"Sarah, the logic says: to have sustained effectiveness and impact, you need protection and safe relationships. What's the belief underneath that? Why do you believe you need C to achieve A?"

This takes longer. The adaptive assumption is often unconscious—a belief so fundamental we don't even see it as a belief.

"I suppose…" Sarah says slowly, "I believe that if people don't like me, I can't be effective. That my effectiveness depends on being liked. On not making waves."

We dig further.

"And underneath that?"

A long pause. "I think I believe that my value comes from being helpful and agreeable. That's what makes me valuable. If I'm difficult or challenging, I lose what makes me… me."

A-C Assumption (Adaptive): My value and effectiveness depend on being liked and agreeable. If I challenge or create discomfort, I lose what makes me valuable.

This is the belief that keeps Sarah stuck. It's not wrong—it served her well for years. It helped her build genuine relationships and a reputation for collaboration. But it's now too small. It can't accommodate the demands of senior leadership, where challenge and advocacy are expected, not threatening.

"Where did you learn that?" I ask quietly. "That your value comes from being agreeable?"

Sarah sits with the question. Then her face shifts—recognition.

"I was 26. My first management role. There was a senior leader—very respected, very powerful—who was making a decision I knew was wrong. I'd done the analysis. I had the data. I spoke up in the meeting."

She pauses.

"He smiled at me. Said 'I appreciate your enthusiasm, Sarah.' Then proceeded as if I hadn't spoken. After the meeting, my manager pulled me aside. Told me I needed to be more careful. That I'd embarrassed myself. That challenging senior leaders publicly wasn't how things worked here."

Another pause.

"The decision went ahead. It failed, exactly as I'd predicted. But no one remembered that I'd raised concerns. What they remembered was that I'd been 'difficult.' For the next year, I was excluded from key meetings. My ideas were dismissed. I learned very clearly: speaking up costs you. Being agreeable keeps you safe."

There it is. The moment the assumption formed. Not from weakness or irrationality—from evidence. From consequence. From legitimate threat.

"And that belief has protected you for how long?"

"Fifteen years," she says quietly.

Step 9 (continued): Challenging the A-C Assumption

This is where everything can shift.

Sarah now sees her assumption not as a character flaw or weakness, but as learned wisdom. At 26, in that specific context, with that particular senior leader and that organisational culture, the belief was correct. Speaking up did cost her. Being agreeable did keep her safe.

But Sarah isn't 26 anymore. She's not a junior manager trying to survive in a toxic culture. She's senior leadership in a different organisation, with fifteen years of proven capability behind her. The context has changed. The question is whether the belief has kept pace.

This is what makes the adaptive assumption different from the technical assumption. We're not looking for alternative tactics. We're asking whether the belief structure itself—forged in one context—still serves in another.

"Sarah," I say, "that belief made perfect sense when you were 26. It protected you from real harm. But you're not in that organisation anymore. You're not that version of yourself. What new belief could we hold now?"

This is the transcendence question. We're not trying to destroy the old belief—it contains truth. We're trying to expand it to include more of what's true now.

"Could it be true," I ask, "that your value comes from more than being agreeable? That effective leaders are valued because they contribute difficult truths, not despite it?"

Sarah sits with this.

"I've seen that. The leaders I most respect aren't the ones who agree with everything. They're the ones who say what needs to be said—but do it in a way that moves things forward."

"So what might a bigger belief look like? One that includes what the old belief was protecting, but opens up new possibilities?"

She thinks. Then:

New Adaptive Belief: My value comes from my whole contribution—including my perspective, my challenge, my advocacy. Being truly helpful sometimes means creating productive discomfort. I can be both kind and clear, both collaborative and challenging.

Sarah sits quietly, then looks up with something like recognition.

"The conflict itself—the tension I've been avoiding—that's actually where the growth is, isn't it? I've been treating it as the problem. But it's showing me exactly what I need to develop. The discomfort of speaking up when I'm afraid is the very thing that's stretching me into the leader I need to become."

This is the deeper insight. The conflict isn't just something to resolve—it's the growth engine itself. What Sarah has been running from is precisely what's calling her forward.

This is transcendence. The new belief doesn't abandon C (protection, relationships)—it expands C to include B (contribution, challenge). Sarah can now see that authentic contribution is a form of collaboration. That respectful challenge is kind. That her value isn't diminished by speaking up—it's enhanced.

Sarah has evaporated her conflict.

Phase 3: Creating Sarah's Solution

Step 10: Create the Solution

Now comes the integration. We've challenged the adaptive assumption and Sarah has found a bigger belief—one that honours both her need for relationships and her need to contribute fully. But beliefs alone don't create change. She needs concrete approaches that express this new understanding.

"Sarah, remember those technical options we generated earlier? The ways you could speak up while maintaining relationships?"

She nods. "The framing things as questions, building alliances, all of that."

"Right. At the time, you said they felt like tricks. Like manipulation. But that was when you still believed your value came from being agreeable. Given this new belief—that your full contribution is your value—let's look at those options again. Which ones now feel possible? Which ones feel like authentic expressions of who you are?"

Sarah looks at the list we created during Step 8. Something has shifted in her face.

"Frame challenges as building on others' ideas..." she reads slowly. "That doesn't feel like a trick anymore. It feels like... actually that's what I'd be doing. I wouldn't be opposing their thinking—I'd genuinely be building on it. Adding the customer reality they might not see."

"What else?"

"Preparing key points before meetings. When I thought speaking up was inherently risky, preparation felt like armouring up for battle. But now it feels like... it's just being ready to contribute well. The way I'd prepare for any important conversation."

Her pace picks up as she works through the list.

"Starting with smaller stakes—that's not avoiding the hard conversations. It's building the muscle. Practicing. Getting comfortable with the discomfort." She smiles slightly. "And connecting concerns to shared outcomes—that's not manipulation. That is the outcome. I care about the customer experience because it matters to all of us, not just to manipulate them into listening to me."

"Keep going."

"Acknowledging others' perspectives before adding mine. When I thought I had to choose between being agreeable and contributing, that felt like a tactic. But it's not. It's actually respecting that they have legitimate viewpoints and I have legitimate viewpoints. Both can be true."

The technical approaches haven’t changed. Sarah’s relationship to them has. What felt like manipulation inside a too‑small belief now feels like authentic leadership inside a bigger one.

"So what's your solution?" I ask. "Not mine. Yours."

She thinks for a moment, then begins.

"The foundation is the belief we just discovered: my value comes from my whole contribution—including my perspective, my challenge, my advocacy. Being truly helpful sometimes means creating productive discomfort. I can be both kind and clear, both collaborative and challenging."

"And supported by?"

"Concrete approaches that express that belief."

Sarah's Solution:

The adaptive foundation: My value comes from my whole contribution. Being truly helpful means contributing my perspective clearly, even when it creates discomfort. I can be both kind and clear, both collaborative and challenging.

Supported by technical approaches, in the order she'll need them:

1. Prepare key points before meetings so contribution feels natural
2. Start with smaller stakes to build the muscle
3. Connect concerns to shared outcomes everyone cares about
4. Acknowledge the validity of other perspectives while adding her own
5. Frame challenges as building on others' ideas, not opposing them

She orders them herself. Preparation comes first, because nothing else works if she arrives composing her words under pressure. Smaller stakes come next, because the muscle has to exist before the big moments arrive. The other three she'll draw on every time she speaks.

"Now," I say, "let's check this against reality. Remember those Undesirable Effects we captured earlier — the costs of the conflict? Go through them with this new belief and these approaches. Which ones would you expect to evaporate?"

Sarah reads down the list. With each one, the same logic holds: when she contributes early, frames her concerns around shared outcomes, and stops monitoring whether it's safe to speak, the cost falls away. The exhaustion goes, because there's no longer an internal battle to fight. The preventable messes get caught before they form. Her team is represented, and the customer perspective is finally in the room when decisions are made.

She slows at one. "Inauthenticity and imposter syndrome — that's the big one. The imposter feeling comes from knowing I'm not showing up as the person I actually am. If I'm contributing fully — kind and clear, collaborative and challenging — then I am that person. The gap between who I am and who I'm performing as... it closes." And as that gap closes, confidence builds with each meeting instead of draining away — and no one could mistake her for someone who isn't contributing.

I let the moment settle. "So how many of those seven UDEs does your solution address?"

"All of them," she says. "Every single one."

Sarah is quiet for a moment, looking at the UDE list and then back at her solution.

"I've been trying to fix these one at a time," she says slowly. "The exhaustion—I tried meditation. The imposter syndrome—I read books about confidence. The team frustration—I tried to compensate by being more available outside meetings. I had seven separate problems and I was looking for seven separate solutions."

She shakes her head.

"But they were never seven problems. They were seven symptoms of the same thing. One belief, producing all of it. Change the belief, and they all dissolve together."

"That's how you know the cloud has truly evaporated," I say. "The solution doesn't just dissolve the conflict in theory—it eliminates the real-world costs that made it worth solving in the first place."

Sarah sits back, looking at the evaporated cloud. There's something different about her—a settledness that wasn't there two hours ago. But then she shakes her head slightly.

"This is still going to be hard, though," she says. "I can see it all clearly now—the belief, the pattern, why I do what I do. But when I'm sitting in that meeting on Monday morning and the COO is talking and I feel that tightening in my chest... knowing all this doesn't make the tightening go away."

"No," I agree. "It doesn't."

"So what do I actually do in that moment? When I can feel the old pull and the new understanding at the same time?"

"That's exactly the right question," I say. "And it's what we're going to work on now. We need to give you something to reach for in the moment. When you're sitting in that meeting and you feel the old pull to stay quiet—the tightening in your chest, the voice telling you to keep your head down—you need something to remember. Not a technique. An objective."

"An objective?"

"A short statement that captures what you're actually here to do. Something that reminds you of the bigger belief, not the old one. Something you can say to yourself in the three seconds between the impulse to stay quiet and the choice you make next."

She thinks about this. "So not 'speak up' or 'be brave'—those are just instructions."

"Exactly. Those push against the old belief. They're willpower. What we want is something that pulls you toward the new one. Something that answers the question: what am I really here for?"

Sarah looks at her cloud—at A, at the new belief, at the solution we've just built.

"My value comes from my whole contribution," she says slowly. "And I'm the only person in that room who sees the customer reality. Nobody else has fifteen years of knowing what actually happens to customers when a decision hits the ground." She pauses. "So the objective would be something like... Provide the scrutiny no one else can."

She tests it. Says it again, quieter.

"Provide the scrutiny no one else can. That's not asking permission to speak. That's my job. That's what my position exists for. The leadership team literally cannot scrutinise decisions from the customer perspective without me. If I stay quiet, that scrutiny doesn't happen."

"How does that feel?"

"It feels like a responsibility, not a risk. When I thought of it as speaking up, it felt like something I might get punished for. But scrutiny? That's what a senior Customer Experience leader is supposed to do. It's not optional. The organisation needs it from me."

"That's the difference between an objective and an instruction," I say. "An instruction tells you what to do—'speak up,' 'be brave.' An objective tells you what your role demands. When the trigger hits—when you feel that old pull to stay quiet—you don't have to fight it. You just have to remember: Provide the scrutiny no one else can. The old belief says your value comes from being agreeable. The objective says your value comes from the unique perspective you hold. You can't hold both at the same time. The objective replaces the trigger."

Sarah nods. "And it's not just about me. If I don't provide that scrutiny, the team suffers. Decisions go unchecked. Problems that I could have caught don't get caught. My silence isn't protecting anyone—it's failing them."

"That's what makes it an objective rather than a personal ambition," I say. "It serves everyone. The leaders get better decisions. Your team gets represented. The organisation gets the customer scrutiny it's missing. And you get to show up as the leader you actually are."

"Something truer than the fear," she says quietly. "The fear is based on a belief that was right when I was 26. The objective is based on what's true now."

I let the silence hold for a moment. Sarah is already reaching for her notebook.

"I want to write this up," she says. "All of it. The cloud, the belief, the objective, the approaches—as a development plan. Something I can come back to when Monday morning arrives and the old pull kicks in."

"What would you include?"

"The belief. The objective. The technical approaches and how they connect to the belief—why they're authentic now, not tricks. And the UDEs." She taps the list. "What it costs me when the old belief wins. That's my reminder of why this matters."

"That's exactly right," I say.

"I think I've known what to write for a while," she says. "I just didn't have the structure to hold it all together."

"Now you do."

One last question before we finish. "What will you do in the next forty-eight hours?"

She doesn't hesitate. "Write the plan tonight. And before Monday's meeting, read the agenda and prepare my two key points."

A TRIP doesn't end with an insight. It ends with a first action the person owns, and Sarah has just named hers.

Sarah isn't being asked to overcome fear through willpower. She isn't being told to "just speak up" or "be more confident." She's not learning tricks to manipulate people into listening.

Instead, she's outgrowing a belief that's become too small. And as the belief expands, different actions become not just possible but natural. The techniques that felt manipulative now feel authentic because they're aligned with a belief structure that can hold her full complexity—collaborative and challenging, kind and clear, protective of relationships and committed to contribution.

The solution isn’t “speak up more.” It’s a different way of understanding what speaking up is for. Sarah isn’t overcoming fear—she’s outgrowing a belief that once served but can no longer contain who Sarah is becoming.

What Happened Next

Sarah wrote her development plan that evening. She told me later that it took less than an hour—the structure was already clear in her mind. The cloud diagram. The old belief and where it came from. The new belief. The objective: Provide the scrutiny no one else can. The technical approaches, and why they were authentic now, not tricks. And at the bottom, the seven UDEs—the cost of staying silent. Her reminder of what was at stake every time the old pull kicked in.

She kept it in the front of her notebook.

The first leadership meeting was on a Monday. Sarah told me about it later.

"My heart was pounding. The COO was presenting a plan to widen our delivery window from next-day to two days across the network, to cut cost, and I could see immediately what it would do to the customer experience. The old feeling hit—the tightening in my chest, the voice saying don't make waves. I actually opened my notebook to the development plan. I read the objective. Provide the scrutiny no one else can. And I thought: if I don't say this, nobody will. We'll repeat last quarter's mistake, and my team will spend months handling the fallout all over again."

She spoke up. Not with a challenge. With a question grounded in data—exactly the kind of contribution she'd identified in Step 8, but now it didn't feel like a technique. It felt like her job.

"I said, 'Can I share something from the customer side? When we narrowed the tracking updates last quarter, complaints and churn both rose within weeks. Our customers read any reduction in the promise as a broken promise. What happens to retention if we widen the delivery window before we've understood that?'"

The room went quiet for a moment. Then the COO leaned forward. "Tell me more about the churn data."

"After the meeting," Sarah said, "two peers came to find me separately. Both said the same thing: they'd been thinking it but hadn't wanted to say it. One of them said, 'I'm glad someone finally brought the customer reality into the room.'"

That phrase stayed with her. The customer reality. It wasn't dissent. It wasn't challenge. It was the thing the room needed that only she could provide.

Over the following weeks, Sarah referred back to her development plan regularly—sometimes before meetings, sometimes after, when the old doubt crept in and she needed to remember why this mattered. The UDE list was particularly powerful. On the mornings when she felt the pull to stay quiet, she would read through the seven costs and ask herself: Do I want to go back to that?

The answer was always no.

Six months later, Sarah sent me a longer update.

"It's not that I never feel nervous now. I do. But the nervousness isn't about whether I should speak—it's about how to say it well. That's a completely different problem. A problem I can solve."

She continued: "The development plan changed too. I don't read it before every meeting anymore—I don't need to. The objective lives in my head now. But I still look at it when something big is coming, or when I've had a difficult interaction and the old belief tries to reassert itself. It's like a map I drew of territory I've now walked. I know the landscape, but the map reminds me where I've been and why I'm not going back."

The most telling detail came at the end of her message: "Last week, a new member joined the leadership team. After the meeting, she pulled me aside and said, 'I can see you're the one who keeps this group honest. That's really valuable.' I nearly laughed. A year ago, no one would have described me that way. Not because I've become someone different—but because I finally became visible as the person I already was."

Sarah didn't become a different person. She became more fully herself. The collaborative, relationship-building strengths she'd always had were now joined by clear advocacy and confident contribution. Both/and, not either/or.

This is what evaporating a cloud looks like in practice. Not willpower. Not motivation. Not positive thinking. But a genuine shift in the belief structure that was maintaining the conflict.

The TRIP in Summary

Let's consolidate what we've seen — the ten steps of the Perry Approach, run end to end:

Phase 1: Building the Cloud (Steps 1–7, Chapters 4–10)

• Step 1. Identify the current state (D′)
• Step 2. Articulate the future state (D)
• Step 3. Surface hidden benefits of future state (B)
• Step 4. Surface hidden benefits of current state (C)
• Step 5. Find the unified outcome (A)
• Step 6. Read the cloud — verify the logical structure by reading back the cloud to check it holds.
• Step 7. Identify the Undesirable Effects (UDEs) — the cost of the conflict that makes it worth solving.

Phase 2: Evaporating the Cloud (Steps 8–9, Chapters 11–12)

• Step 8. Challenge the C-D′ assumption (technical): What options exist to maintain C while replacing D′?
• Step 9. The adaptive shift (A→C) — surface the belief connecting your objective to needing C in its current form. Find the bigger C that can include B.

Phase 3: Creating the Solution (Step 10, Chapter 13)

• Step 10. Create the solution — combine the new adaptive belief with the relevant technical options — ordered by prerequisite for fastest implementation — to form a coherent way forward, with first actions the person owns.

The magic isn't in any single step. It's in the integration—technical solutions supported by adaptive belief change. Neither alone is sufficient. Together, they create lasting transformation.

What a TRIP Leaves Behind

Every TRIP, at any level, ends with the same things in hand. Sarah's had all of them:

• The cloud itself — built, read back and checked: her map of the conflict.
• The Conflict Tax made visible — her seven UDEs, in her own words.
• A dual-track solution — the technical approaches and the adaptive shift that makes them genuine rather than performed.
• An artefact she keeps — her development plan, at the front of her notebook.
• A first action she owns — two prepared points for Monday's meeting.

Sarah's was a TRIP at its first level: one stakeholder, one cloud. The same ten steps run when two parties sit across a table — a manager and a colleague, Finance and Operations, a company and a union — and when a whole team is in the room. The method doesn't change as the stakes grow. What grows is the number of legitimate logics that have to be held at once.

Why This Works When Other Approaches Fail

Traditional approaches fail Sarah for predictable reasons:

"Just speak up" ignores the needs that staying quiet protects—willpower against psychology, and psychology wins.

"Build confidence first" puts the cart before the horse. Confidence comes from action, but action feels impossible without the belief shift.

"Practice assertiveness techniques" offers technique without the belief change, so it feels inauthentic—it contradicts her sense of how value works.

A TRIP works because the method underneath it honours the whole system: Sarah is doing the best she can with the beliefs she holds. Change the beliefs, and different actions become not just possible, but natural.

Your Turn

Before we move to Chapter 4, where you'll learn to identify your own D′, take a moment to reflect:

1. Think of a behaviour you've been trying to change. Something you know you "should" do differently but can't seem to shift.
2. What is that behaviour protecting? What would you lose if you changed? Be honest—there's always something.
3. What belief might be keeping those benefits tied to your current approach? What do you believe must be true for your current behaviour to be the only option?
4. Could that belief be expanded? Not abandoned—expanded. What bigger belief might honour what you're protecting while opening new possibilities?

You don't need to solve it yet. Just notice. The full methodology will guide you through systematically in the chapters ahead.

What's Next

In Chapter 4, you'll learn to identify your own D′ — the first step in building your own cloud. Everything you need is in the next chapter. You can work through it on your own, at your own pace.