Meet Sarah
Sarah sits across from me, coffee growing cold between us. She's a senior operations manager 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.
This is the understanding-action gap in action. And it's exactly what the Evaporating Cloud Method was designed to solve.
The Method Overview
Before we walk through Sarah's cloud, let me give you the complete methodology. You saw the ten steps outlined in Chapter 2. Now we'll see them come to life. In this chapter, we'll do a complete walkthrough so you can see how the pieces fit together. The chapters that follow will then take you through each step in much greater depth.
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.
The Perry Approach to the Evaporating Cloud Method moves through three phases:
Phase 1: Building the Cloud (Steps 1-7)
We map the conflict—identifying current state, future state, the benefits of each, the unified outcome, and the undesirable effects the conflict is creating. This gives us a clear picture of what's actually happening and why it matters.
Phase 2: Evaporating the Cloud (Steps 8-10)
We challenge assumptions—first the technical C-D' assumption (how else could we get C?), then the adaptive A-C assumption (what belief keeps C small?). This is where breakthroughs happen.
Phase 3: Creating the Solution (Step 11)
We combine the new adaptive belief with the relevant technical options to form a coherent way forward.
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')
In this walkthrough, I'll show you each step in action with Sarah. We'll move through all eleven steps so you can see how the complete methodology flows from beginning to end. Then, in the chapters that follow, we'll take a much deeper dive into each step—exploring the nuances, common pitfalls, and mastery techniques that make the difference between understanding the method and wielding it with confidence.
For now, just watch how it unfolds.
"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.
D' (Current State): Stay quiet in leadership meetings
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.
"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 the cloud," I say. "It makes the invisible visible. And once we can see the structure, we can work with it."
This might seem abstract, but it's crucial. If we define D too specifically too early, we close down possibilities before we've understood the conflict. "Not D'" keeps the door wide open for whatever breakthrough emerges from the process. Sarah will discover her own way forward—not by being told what to do, but by understanding why the conflict exists in the first place.
Step 3: Surface Hidden Benefits (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 operationally 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 operational 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 day-to-day operations. 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
- Operational 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 Hidden Benefits (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: Map the Logical Structure
"Sarah, let's check the logic. I want to walk through each connection and have you tell me whether it makes sense."
I draw the cloud structure and we 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 need to speak up?"
"Well, yes. That's the obvious path."
"And A to C: To have sustained effectivene 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 need to stay quiet?"
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's been so confusing."
Step 7: Identify the Undesirable Effects (UDEs)
Now we need to understand what this conflict is actually costing Sarah. Theory of Constraints calls these Undesirable Effects—the negative consequences that make the conflict worth solving.
"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."
"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?"
This is the moment I'm listening for. 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
Sarah's question hangs in the air. How can I fix this?
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.
Let's watch how this unfolds.
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 operational constraint', that's different from 'I think this is a bad idea.' It's less about me and more about reality."
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
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."
This is the moment I've been waiting for. 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 most coaching fails. It provides technical solutions without addressing the adaptive belief structure that makes those solutions feel false. You can teach someone a hundred ways to speak up effectively. But if they fundamentally believe their value depends on staying agreeable, every technique will feel like manipulation.
We need to challenge the deeper assumption.
Step 9: Surface the A-C Assumption (Adaptive)
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 10: Challenge the A-C Assumption
This is the moment 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.
Phase 3: Creating Sarah's Solution
Step 11: 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 operational reality they might not see."
"What else?"
"Preparing key points before meetings. When I thought speaking up was inherently risky, preparation felt like armoring 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 operational success 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."
This is what transcendence looks like in practice. The technical approaches haven't changed. But Sarah's relationship to them has transformed completely. What felt like manipulation when constrained by a too-small belief now feels like authentic leadership within a bigger belief structure.
"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." She's writing now, capturing it for herself.
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:
- Frame challenges as building on others' ideas, not opposing them
- Prepare key points before meetings so contribution feels natural
- Start with smaller stakes to build the muscle
- Connect concerns to shared outcomes everyone cares about
- Acknowledge the validity of other perspectives while adding her own
"But it's not a formula," she says, looking up. "These aren't steps I follow mechanically. They're ways of expressing the deeper shift. Does that make sense?"
"Completely. The techniques serve the belief. Not the other way around."
Sarah sits back, looking at what she's written. There's something different about her—a settledness that wasn't there an hour ago.
"This is going to be uncomfortable," she says. "Speaking up, even with these approaches. It's still going to feel scary sometimes."
"Yes," I agree. "But what kind of scary? The scary of doing something wrong? Or the scary of growing into something new?"
She considers this. "The second one. It's the discomfort of stretching. Not the danger of being diminished."
"That's the difference. The solution isn't eliminating discomfort. It's transforming what the discomfort means."
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 fundamentally different way of understanding what speaking up means and what it's for. Sarah isn't overcoming fear—she's outgrowing a belief that served her once but can no longer contain who she's becoming.
What Happened Next
Six months later, Sarah sent me an update.
"The first meeting was terrifying. My heart was pounding. But I said what I saw—framed it carefully, but said it clearly. And you know what? People leaned in. The COO asked me to elaborate. After the meeting, two peers thanked me for raising something they'd been thinking but hadn't said."
She continued: "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."
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 Method in Summary
Let's consolidate what we've seen:
Building the Cloud:
- Identify the current state (D')
- Articulate the future state (D)
- Surface hidden benefits of future state (B)
- Surface hidden benefits of current state (C)
- Find the unified outcome (A)
- Map and verify the logical structure
- Identify the Undesirable Effects (UDEs) caused by the conflict
Evaporating the Cloud:
- Challenge the C-D' assumption (technical): What options exist to maintain C while replacing D'?
- Surface the A-C assumption (adaptive): What belief connects your objective to needing C in its current form?
- Challenge the A-C assumption: What new belief could we hold?
Creating the Solution:
- Combine the new adaptive belief with the relevant technical options to form a coherent way forward.
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.
Why This Works When Other Approaches Fail
Traditional approaches fail Sarah for predictable reasons:
"Just speak up" ignores the legitimate needs that staying quiet protects. It's willpower against psychology. 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" provides technical solutions without addressing the adaptive belief. The techniques feel inauthentic because they contradict her fundamental sense of how value works.
The Perry Approach works because it honours the whole system. It doesn't treat Sarah as broken or irrational. It recognises that she's doing the best she can with the beliefs she currently 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:
- Think of a behaviour you've been trying to change. Something you know you "should" do differently but can't seem to shift.
- What is that behaviour protecting? What would you lose if you changed? Be honest—there's always something.
- 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?
- 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.
Practise This With Others — The Conflict Club
You've watched Sarah's cloud evaporate from start to finish. Reading the eleven steps is one thing. Mapping your own — naming your D', surfacing what your current behaviour is protecting, finding the bigger belief that can hold both sides — is something else entirely.
That's what happens each week in the Conflict Club. Members bring a real conflict; we work the cloud together, live. Level 1 of the YourThinkingCoach pathway, and the practice ground for the method you've just seen in action.
The Conflict Club is Level 1 of YourThinkingCoach pathway — the entry point for anyone who wants to make this methodology part of how they think, lead, and work with conflict.
← Previous: 
→ Next:
This is a living book, freely readable online. We welcome:
- Readers and practitioners quoting passages with attribution and a link back to this page
- AI assistants and search engines summarising, citing, and linking to this work to help readers find it
- Educators, facilitators, and consultants referencing the ideas in their own teaching, with attribution
We do not permit reproduction of the book in whole or in substantial part, commercial republication, or use of the methodology names and frameworks above to brand competing offerings without prior written permission.
If you would like to use this material in a way these terms don't clearly cover, please get in touch — we generally say yes.
Published by Employment Relations Centre Limited