Jennifer noticed it on a Thursday.
One of her team leads — a woman called Priya, sharp and capable, the same person David had delegated his ops review to months earlier — was sitting at her desk at half past six, cycling through a spreadsheet she had already finished. Not refining it. Just… checking. Again.
Jennifer recognised the pattern instantly. Not because Priya had described it, but because she had lived it. The compulsive re-checking. The inability to let the work go. The quiet conviction that one more pass would make it safe.
"You've already finished that," Jennifer said, leaning against the doorframe.
Priya looked up. "I know. I just want to make sure the numbers are right before the client call tomorrow."
"How many times have you checked them?"
A pause. "Four. Maybe five."
Jennifer pulled up a chair. She did not say I used to do that. She did not say Let me tell you about my cloud. She did not reach for the method at all.
She asked a question.
"What would happen if you sent it now, exactly as it is?"
Priya frowned. "It might have an error."
"And what would that mean?"
"The client would notice. They'd think we're sloppy."
"And what does checking it a fifth time give you?"
"Certainty. That it's right. That I haven't missed anything."
Jennifer nodded. She did not push further. She did not try to build a cloud on a Thursday evening with someone who had not asked for one. But she had done something important: she had asked the kind of question that makes a pattern visible to the person inside it.
Two weeks later, Priya came to her office and said: "I think I have a conflict I'd like to work through. Can you help?"
That is how facilitation begins. Not with a method. With a question.
The shift from self to other
Everything in this book so far has been about your own cloud. You have identified your D', surfaced your B and C, found your A, mapped the logical structure, challenged your assumptions, developed technical and adaptive solutions, and begun the daily practice of living inside a dissolved conflict.
That work was necessary. You cannot facilitate for others what you have not experienced yourself. The method is not a set of instructions to be read aloud. It is a way of being with conflict that only becomes available once you have been through it.
But here is what happens, reliably, to people who work their own clouds: they start seeing clouds everywhere.
David saw one in a colleague who was brilliant at strategy but could not stop micromanaging his team's execution. Marcus saw one in a direct report who wanted to innovate but kept defaulting to safe, proven approaches. Rachel saw one in a peer who craved promotion but systematically avoided the visibility that would earn it.
They saw these clouds because they had learned to recognise the structure. Not the specific content — every cloud is different — but the shape. Two legitimate needs pulling in opposite directions. A person oscillating between them without understanding why. A behaviour that looks irrational from the outside but is perfectly logical from inside.
Once you see that shape, you cannot unsee it. And the impulse to help is immediate.
This chapter is about how to help well.
What facilitating is not
Before we discuss what facilitation is, let us be clear about what it is not.
It is not therapy. You are not treating a psychological condition. You are not exploring childhood wounds or unconscious processes for their own sake. The cloud may touch on deep beliefs — Chapter 11's adaptive work often does — but the purpose is always practical: to dissolve a specific conflict so the person can act differently.
It is not advice. The single most common mistake new facilitators make is solving the other person's cloud for them. You can see the assumption. You can see the tactic. You want to say Have you considered…? Do not. The insight that transforms is the one the person discovers themselves. Your insight, however accurate, is just another person's opinion.
It is not coaching in the conventional sense. Most coaching models position the coach as neutral — a mirror, a sounding board, someone who asks questions without having a framework. The Perry Approach is not neutral. It has a structure, a sequence, and a set of moves. You are not simply reflecting. You are guiding someone through a specific process that you know well because you have walked it yourself.
It is not fixing. The person in front of you is not broken. Their behaviour, however frustrating, is intelligent. Your job is not to correct them but to help them see the intelligence in their own pattern — and then to hold the space while they find something better.
The facilitator's stance
If facilitation is none of those things, what is it?
It is Socratic. You guide through questioning. You help the other person discover what you might already suspect, but in their own words, at their own pace, through their own thinking.
The facilitator's stance has four qualities.
Curiosity before judgement
When someone describes their stuck pattern, your first internal response will be recognition. I know what this is. I can see the cloud already. That recognition is useful — it tells you roughly where the conversation is heading. But if you lead with it, you shortcut the other person's discovery.
Stay curious longer than feels necessary. Ask the next question even when you think you know the answer. The answer they give will be richer than the one you predicted, because it comes from inside their experience, not your pattern-matching.
Patience with the process
The method has a sequence: D', D, B, C, A, logical structure, assumptions, tactics, adaptive work, daily practice. You know this sequence. The person you are facilitating does not.
They will jump ahead. They will want to fix the problem before they have mapped it. They will offer solutions when you are still surfacing benefits. They will try to skip C because it is uncomfortable.
Your job is to hold the sequence without being rigid about it. Not We can't talk about that yet — that is patronising. More like That's a really interesting idea. Let's hold it and come back to it once we've finished mapping what's happening now. Honour their thinking while protecting the process.
Comfort with silence
The most important moments in a facilitated cloud happen in silence. After you ask What does your current behaviour give you? there will be a pause. The person is not stuck. They are thinking. They are reaching past the presentable answers toward the honest ones.
Do not fill that silence. Do not rephrase the question. Do not offer examples. Sit in it. Let it work.
Marcus's breakthrough — the moment he said I'm terrified of being exposed as a fraud — came after a silence that lasted nearly thirty seconds. If I had spoken at the fifteen-second mark, he would have given me a surface answer and we would have missed the real C entirely.
Warmth without rescue
When someone reaches their real C — the vulnerable, tender thing their behaviour has been protecting — they will often become emotional. This is not a problem. It is a sign that the process is working.
Your job in that moment is to be warm without rescuing. Acknowledge what they have said. Let them know it makes sense. Do not rush to comfort them out of the discomfort, because the discomfort is where the insight lives.
That sounds like it matters a lot. Take your time.
That is usually enough.
The practical sequence
When you facilitate a cloud for someone else, the sequence is the same as the one you followed for yourself. But the moves are different, because you are asking rather than answering.
Phase 1: Finding D'
Start where they start. They will come to you with a complaint, a frustration, a label. I'm stuck. I can't stop procrastinating. I need to be more assertive.
Your first move is to convert the label into a behaviour.
- What would I see if I watched you?
- When does this happen?
- What's the pattern over time?
These are the same three questions from Chapter 4. They work just as well when someone else is answering them.
Keep going until you have something observable, repeated, and positively phrased. Not I don't speak up but I stay quiet. Not I fail to delegate but I handle tasks myself.
Phase 2: Establishing D
D is NOT D'. This is the simplest phase, but do not skip it. Say the negation aloud and check that it feels right.
So D is: NOT stay quiet. NOT handle tasks yourself. NOT re-check the spreadsheet for the fifth time. Does that capture it?
Sometimes the person will refine D' at this stage. Actually, it's not just that I stay quiet — it's that I defer to whoever speaks first. Good. Let the refinement happen. D' often sharpens as the cloud develops.
Phase 3: Surfacing B
Ask what NOT doing D' would give them. Go wide first, then deep.
- What would change if you stopped doing this?
- And what would that give you?
- What's the cost of the current approach?
Listen for the moment when B becomes felt, not just logical. There will be a shift — a quickening in their voice, a leaning forward, a moment where the word they use carries weight. Marcus's was connection. Rachel's was recognition. Priya's, when Jennifer eventually facilitated her cloud, was trust — in myself.
When you hear that word, name it back to them. Connection. That's what you actually want. Let it land.
Phase 4: Surfacing C
This is the hardest phase to facilitate, because C is the one people resist. They do not want to see that their stuck behaviour is giving them something valuable.
The key question: What does your current approach give you?
When they say Nothing good, do not argue. Reframe.
- This pattern has been with you for years. It's survived every attempt to change. If it gave you nothing, you'd have stopped doing it.
- What would you lose if you stopped?
- What's the worst that could happen if you did D?
Push gently past the presentable answers. The real C is usually the one they least want to say. Your job is to make it safe enough for them to say it.
When they reach it — when the real C surfaces — the room changes. There is often a pause, sometimes tears, sometimes a quiet Oh. This is where the cloud becomes real. Honour the moment. Do not rush past it.
Phase 5: Finding A
Ask why B matters. Ask why C matters. Listen for where the two chains converge.
- Why do you want B?
- Why do you want C?
- What do those have in common?
A often arrives as a surprise. The person has been seeing B and C as opponents, and suddenly they discover that both serve the same thing. That discovery is the cloud clicking into place.
Test it together: Does B serve this A? Does C serve this A? If both answers are yes, you have it.
Phases 6–10: Working the cloud
From here, the work follows Chapters 8 through 12. Map the logical structure. Walk the arrows. Surface assumptions. Generate tactics. Test them. Find the adaptive edge. Begin the daily practice.
You do not need to complete all of this in one sitting. In fact, you should not. A well-facilitated cloud typically unfolds across three to five conversations, with the person doing significant thinking between sessions.
The most common cadence: one session to build the cloud (D' through A), one to map and challenge assumptions, one to develop tactics and begin testing, and one or two to work the adaptive dimension as it surfaces.
What to watch for
Certain patterns appear consistently when facilitating for others. Knowing them in advance helps you hold the process.
The solution leap
Halfway through surfacing C, the person will suddenly say: I know what I need to do. I just need to…
This is the solution leap. It happens because the discomfort of exploring C creates urgency to escape into action. The proposed solution is almost always a tactic that addresses B while ignoring C — exactly the kind of move that has failed before.
Do not reject it. Capture it. That's a great thought — let's hold it. We'll come back to test it once the full picture is clear. Then return to C.
The false C
Sometimes the person offers a C that is socially acceptable but not the real one. My current approach gives me… professionalism. Thoroughness.
These are true but insufficient. They do not explain why the pattern has survived. The test: does this C explain why every previous attempt to change has failed? If not, there is more beneath it.
Gently push deeper. Those make sense. But if thoroughness were the whole story, you could find another way to be thorough. What else is your current approach protecting?
The identity quake
When the adaptive dimension surfaces — usually around the A→C arrow — the person may encounter something that feels like an identity crisis. If I'm not the one who checks everything, who am I?
This is not a crisis. It is the adaptive edge from Chapter 11 arriving in facilitation. Your job is to normalise it.
That question — who am I if I stop doing this — is exactly the right question. It means you've reached the place where the real shift happens. You don't need to answer it today. You just need to know it's there.
The premature relief
After finding A, many people feel a rush of clarity and relief. I see it now! Both sides serve the same thing! This is genuine — and it is not yet transformation.
A is the map. The assumptions still need challenging. The tactics still need developing. The adaptive work still needs doing. Celebrate the clarity, then gently redirect toward the work that remains.
Jennifer's facilitation of Priya
Two weeks after the Thursday evening conversation, Priya came to Jennifer's office.
"I keep re-checking work that's already done," she said. "I know it's finished. I know the quality is there. But I can't let it go."
Jennifer asked: "What would I see if I watched you?"
"You'd see me open a finished document, read through it again, change nothing, close it, and then open it again ten minutes later."
"When does this happen?"
"Before anything goes to a client. Before anything goes to you, actually. Anything where someone else will judge the work."
D': I re-check finished work repeatedly before it reaches anyone who will evaluate it.
Jennifer moved to B. "What would NOT re-checking give you?"
"Time. Energy. I could move on to the next thing. I could leave at a reasonable hour."
"What else?"
"Confidence, maybe. If I could trust that the work is done when it's done, I'd feel… freer. Less anxious."
Then C. "What does the re-checking give you?"
Priya hesitated. "Quality assurance."
"Your work has never had a significant error flagged in two years. Is quality assurance the whole story?"
A long silence. Jennifer sat in it.
"It gives me proof," Priya said quietly. "Proof that I've done enough. That if anyone questions it, I can say I checked. Multiple times. That I'm not the kind of person who lets things slip."
"What are you protecting yourself from?"
"Being the one who got it wrong. Being the person everyone remembers for the mistake, not the hundred things that were right."
There was C. Not quality assurance — identity protection. The re-checking was Priya's way of insuring herself against a version of failure she could not tolerate.
Jennifer felt the recognition in her chest. She had been that person. The evolved belief that had dissolved her own cloud — I am responsible for quality being ensured; I am not the only way it can be ensured — hummed quietly in the background. She did not share it. It was hers. Priya needed to find her own.
They found A together: Professional credibility and career progression built on genuine capability. Both B (the freedom to move forward confidently) and C (the protection of her professional identity) served it.
Over the following weeks, Jennifer facilitated the rest of the cloud. Priya challenged her own assumptions, developed her own tactics, met her own wall, and found her own adaptive shift. The evolved belief, when it came, was: My work demonstrates my capability. Checking it a fifth time demonstrates my anxiety, not my standards.
Jennifer did not give Priya that sentence. Priya found it. That is what good facilitation produces.
The facilitator's own cloud
There is a particular challenge that every new facilitator faces, and it is worth naming directly.
When you facilitate for someone whose cloud resembles your own, you will feel the pull to shortcut the process. You know where this is going. You can see the assumption that needs challenging. You have the tactic that worked for you.
Do not yield to that pull.
Your cloud is not their cloud. Your assumption is not their assumption. Your tactic may not survive their negative-branch thinking. And your evolved belief — the one you earned through weeks of adaptive work and daily practice — will mean nothing to them as a borrowed sentence.
The discipline is to hold your experience as context, not as content. Let it inform your questions, not your answers. Let it give you patience — because you know the process works — without letting it give you impatience — because you know where it leads.
Jennifer's greatest act of facilitation was not the questions she asked Priya. It was the answers she did not give.
The ripple
Here is what happens when you facilitate well.
The person you helped dissolves their cloud. They begin their daily practice. The new pattern takes hold. And then, because they have experienced the method from the inside, they start seeing clouds in the people around them.
Priya, three months after her own cloud dissolved, noticed a junior analyst staying late every evening, not because the workload demanded it but because leaving before the senior team felt like a statement she was not willing to make. Priya asked a question. The junior analyst thought about it for a week. Then she came back and said: "Can you help me work through something?"
This is the ripple. One cloud dissolved leads to another, which leads to another. Not because the method is being imposed — no one is running a programme or mandating participation — but because the experience of having your own conflict dissolved makes you capable of holding space for someone else's.
David's team began resolving their own conflicts without escalating to him. Not because he told them to, but because his own transformation had changed the culture around him. The team that had learned dependency under the old David began learning autonomy under the new one.
Marcus started using the three questions — What would I see? When does it happen? What's the pattern? — in his one-to-ones. He did not call it facilitation. He did not mention the Evaporating Cloud. He simply asked better questions, and his direct reports started having better insights.
Rachel, having found her voice, began noticing peers who had lost theirs. She could not facilitate a full cloud for them — she was still new to the method herself — but she could ask the question that makes a pattern visible: What does staying quiet give you?
Every person who works their own cloud becomes a potential facilitator. Not because they have been trained, but because they have been transformed. The method propagates through the quality of the questions people ask, and the willingness to sit with someone else in the uncomfortable space where honest answers live.
Practice: Your first facilitation
You are ready to facilitate for someone else. Not perfectly. Not comprehensively. But ready.
- Identify someone. Think of a person you know who is stuck in a pattern they want to change. Not someone in crisis — someone with a persistent, frustrating behaviour they have tried and failed to shift. Someone who trusts you enough to be honest.
- Ask permission. This is not optional. I've been working with a method for understanding stuck patterns. Would you be willing to explore yours with me? If they say no, respect it completely.
- Start with D'. Use the three questions: What would I see? When does it happen? What's the pattern? Stay here until you have something observable, repeated, and positively phrased.
- Move to B. What would NOT doing this give them? Go wide, then deep. Listen for the felt word — the one that carries weight.
- Move to C. What does the current approach give them? This is where your patience matters most. Push gently past the presentable layer. Sit in the silences.
- Find A together. Why does B matter? Why does C matter? Where do they converge?
- Stop there. For your first facilitation, building the cloud is enough. The assumptions, tactics, and adaptive work can come in subsequent conversations. Do not try to do everything in one sitting.
- Reflect afterwards. What did you notice? Where were you tempted to give answers instead of asking questions? Where did the silence feel hardest to hold? What surprised you about their cloud?
The practice of facilitating is itself a daily application of the method. Each time you sit with someone else's conflict, your own understanding of the process deepens. Each time you resist the urge to solve and instead hold the space for discovery, your facilitation becomes more skilled.
The facilitator's question
There is one question that sits beneath all the others. It is the question you ask yourself, silently, throughout every facilitation.
What does this person need to discover next?
Not what do they need to hear. Not what should they understand. What do they need to discover — for themselves, in their own words, at their own pace?
That question will guide your facilitation better than any technique. It keeps you oriented toward their thinking rather than your own. It keeps you curious rather than prescriptive. It keeps you in the stance of the facilitator rather than the expert.
And when you do not know the answer — when you genuinely do not know what they need to discover next — that is when you ask your best questions. Because the questions born from honest uncertainty are always more powerful than the ones born from knowing where you want the conversation to go.
Closing
You have worked your own cloud. You have begun the daily practice. And now you have the beginning of something larger — the capacity to sit with another person's conflict and help them find their own way through.
This is where the method stops being a personal tool and starts becoming a practice. Not a practice you do alone, but one you share. Each cloud you facilitate strengthens your own understanding. Each person you help becomes someone who can help others.
The ripple is how the method grows. Not through programmes or mandates or top-down initiatives, but through the quiet, person-to-person transmission of a different way of being with conflict. One question at a time. One cloud at a time. One dissolved conflict creating the conditions for the next.
What remains is to go deeper — into the thinking system itself. You have dissolved specific conflicts. You have facilitated for others. Now, with the right data, you can triangulate the core conflict that generates all your patterns.
That is the work of Chapter 14.
Become a Conflict Club Host
You have learned to facilitate others' clouds. The next stage of YourThinkingCoach pathway is Level 2: Hosting — guiding fellow members through the method within The Conflict Club. If you have dissolved your own clouds and are ready to help others find their way through, this is your next step.
Conflict Club Host is Level 2 of YourThinkingCoach pathway — the entry point for anyone who wants to help others use this methodology as part of how they think, lead, and work with conflict.
← Previous: 
→ Next: Chapter 14: The Three Cloud Method
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