Chapter 14: The Three Cloud Method

David opened the envelope on a Tuesday morning.

He had completed the Life Styles Inventory™ several weeks earlier — 240 statements, each rated on a scale from one to five. I set my own goals. I go along with others. I need to be the best. I help others think for themselves. Statement after statement, circling numbers at his kitchen table, wondering what a self-assessment questionnaire could possibly tell him that eighteen months of cloud work had not.

The circumplex stared back at him from the page.

It was a circle — twelve segments arranged like a clock face, each representing a different thinking style. Some segments extended far from the centre, like spokes reaching toward the rim. Others barely registered. The shape was jagged, asymmetric, unmistakably his.

What struck him was not the individual scores. It was the pattern.

The styles that extended furthest — the ones dominating his thinking — were clustered at the bottom of the circle. Perfectionistic. Power. Conventional. All security-based. All driven by the need to protect, to control, to maintain.

The styles at the top — Achievement, Self-Actualizing, Humanistic-Encouraging — were present but compressed. Satisfaction-based styles. The ones associated with growth, creativity, connection. The ones he wanted to live in.

"I can see my clouds in this," he said, turning the page toward me. "Every single one."

He was right. And he was about to discover something more powerful than any single cloud had shown him.

A different kind of data

Until this point in the book, every cloud you have built has started from a specific conflict — a behaviour you wanted to change, a tension between two legitimate needs. You noticed the pattern, named D', surfaced B and C, found A, challenged assumptions, developed tactics.

That is powerful work. But it is also reactive. You build a cloud when a conflict presents itself. You dissolve the conflict. You move on until the next one surfaces.

The Life Styles Inventory™ offers something different: proactive data about your entire thinking system.

LSI 1 is a self-assessment of thinking styles. You rate 240 statements about how you think and behave. The results are plotted on the Human Synergistics Circumplex — a circle divided into twelve thinking styles, arranged along a vertical axis that runs from security at the bottom to satisfaction at the top.

The circumplex does not tell you what is wrong with you. It shows you how you think — which patterns dominate, which are underdeveloped, and where the tensions in your system live.

And those tensions are clouds. Waiting to be built.

The circumplex in brief

The twelve thinking styles on the circumplex fall into three clusters.

Every person has a profile across all twelve styles. The question is not whether you use defensive styles — everyone does. The question is which ones dominate your thinking, and what that dominance is costing you.

Your LSI 1 circumplex is a photograph of your thinking system. The three cloud method turns that photograph into a development plan.

The method

The three cloud method is a way of looking at your personal system and triangulating your core conflict.

Here is how it works.

You take your LSI 1 results and choose three styles:

1. Two security-based styles to reduce — your personal brakes
2. One satisfaction-based style to increase — your personal accelerator

For each of the three, you build an Evaporating Cloud.

The two brake clouds show you what your defensive thinking is protecting and what it is costing you. The accelerator cloud shows you what is preventing you from growing into the thinking style you most want to develop.

When you lay the three clouds side by side, something emerges that no single cloud could reveal: the common assumptions that run through all three. The shared beliefs that hold the entire pattern in place. The core conflict in your personal system.

This is triangulation. Three different angles on the same underlying structure.

Choosing your three styles

When David looked at his circumplex, the choices were clear. But for many people, the selection requires thought. Here are the principles.

The two brakes

Look at your security-based styles — both Passive/Defensive and Aggressive/Defensive. Which two are most elevated? Which two are creating the most cost in your work and relationships?

The two highest scores are usually the right starting point, but not always. Sometimes a moderately elevated style is causing more damage than a highly elevated one because of where it shows up. A moderately high Power style that activates specifically with direct reports may be more costly than a highly elevated Perfectionistic style that you manage well in most contexts.

The test: Which two defensive styles, if I could reduce them, would make the biggest difference to how I work and how others experience me?

For David, the answers were Perfectionistic and Conventional.

Perfectionistic was his most elevated style — the relentless standards, the need to check everything, the inability to let work leave his hands until it was flawless. This was the engine behind his original cloud. His refusal to delegate was not about control for its own sake. It was about the terror that someone else's work would not meet the standard, and that the failure would be his.

Conventional was his second brake — less obvious but equally powerful. David followed organisational norms with quiet rigidity. He did things the way they had always been done. He deferred to hierarchy. He maintained processes that no longer served the work because changing them felt like breaking a contract with the system that had promoted him.

The accelerator

Now look at your constructive styles. Which one, if you could develop it more fully, would most transform your effectiveness?

This is not about which constructive style you score highest on. It is about which one, if amplified, would create the greatest positive shift in how you lead, work, and relate.

For David, it was Humanistic-Encouraging. His evolved belief from Chapter 11 — my role is to build capability, not to demonstrate my own — was already pointing him toward this style. But his circumplex showed it was still compressed, still fighting for space against the Perfectionistic and Conventional patterns that had dominated his thinking for twenty years.

Humanistic-Encouraging was not just a style David wanted. It was the style his team needed from him. The accelerator is often the style that would benefit not only you but the entire system around you.

Cloud 1: The Perfectionistic brake

David built his first cloud with me over two sessions.

D': I set standards that require personal verification of all significant outputs.

D: NOT set standards that require personal verification of all significant outputs.

We went to B. "What would NOT doing this give you?"

"Time. Capacity. My team would develop faster because they'd be doing the work, not watching me re-do it. I'd be able to focus on strategy instead of execution. I'd probably sleep better."

B: The capacity to lead strategically and develop my team's capability.

Then C — the harder question. "What does your perfectionistic standard-setting give you?"

David had been through this before with his delegation cloud. But the LSI framing surfaced something new. "It's not just about quality. It's about…" He paused. "If the standard is mine, then the identity is mine. I'm the person who gets it right. That's who I am in this organisation. That's who I've always been."

C: A professional identity built on personal excellence and reliability.

A: Sustained high performance and career fulfilment.

The assumption in the C→D' arrow: The only way to maintain my professional identity is to personally verify that everything meets my standard.

David stared at it. "I've seen this before. In my delegation cloud. But this is… wider. This isn't about one behaviour. This is about how I think about everything."

That is what the LSI cloud does differently. When you build a cloud from a specific conflict, you get the specific assumptions. When you build a cloud from a thinking style, you get the systemic assumptions — the ones that generate multiple specific conflicts.

Cloud 2: The Conventional brake

The second cloud came faster. David was learning the rhythm.

D': I follow established procedures and organisational norms even when they no longer serve the work.

D: NOT follow established procedures and organisational norms when they no longer serve the work.

B: The freedom to innovate, adapt, and lead change that improves outcomes.

C — and here David surprised himself. "It gives me belonging. If I follow the rules, I belong. I'm a good member of the system. I don't make waves. I don't draw the wrong kind of attention."

C: Belonging and acceptance within the organisational system.

A: Sustained high performance and career fulfilment.

The same A. Already, the triangulation was beginning.

The assumption in C→D': The only way to maintain belonging in this organisation is to follow established norms. Deviation means exclusion.

"Is that true?" I asked.

"No," David said slowly. "The people I most respect here are the ones who challenge things constructively. The CEO didn't get where she is by following conventions. But somehow I've been operating as if the rules apply differently to me."

Cloud 3: The Humanistic-Encouraging accelerator

The accelerator cloud has a different shape. Instead of mapping a style you want to reduce, you map the obstacles to a style you want to increase.

D': I focus on task outcomes rather than on developing the people doing the tasks.

D: NOT focus on task outcomes rather than on developing the people doing the tasks. Which operationally means: make people development the primary lens through which I approach my work.

B: A team that grows in capability, confidence, and autonomy — and outcomes that improve because the people producing them are improving.

This was the future David could see. The one his dissolved delegation cloud had pointed him toward. But the circumplex showed him he was not there yet. The Humanistic-Encouraging style was still compressed. Something was holding it down.

C: "What does focusing on task outcomes give me?"

"Measurable results. Things I can point to. Evidence that I'm performing."

C: Tangible, measurable evidence of my contribution and value.

A: Sustained high performance and career fulfilment.

The same A again. Three clouds. One unified outcome. Three different conflicts. And now the assumptions were laid bare.

The assumption in C→D': The only way to demonstrate my value is through measurable task outcomes. Developing people is invisible work that won't be recognised or rewarded.

Triangulation: The core conflict

David laid the three clouds side by side on my desk. Three sheets of paper, three structures, three sets of assumptions.

Cloud 1 (Perfectionistic): The only way to maintain my identity is to personally verify everything.

Cloud 2 (Conventional): The only way to belong is to follow the rules.

Cloud 3 (Humanistic-Encouraging): The only way to demonstrate value is through measurable task outcomes.

"They're the same assumption," David said quietly. "Wearing different clothes."

He was right. Beneath all three was a single core belief:

This is what triangulation reveals. No single cloud could have surfaced this with such clarity. The delegation cloud showed one facet. The Perfectionistic cloud showed another. The Conventional cloud a third. But it was only when all three were laid side by side that the core belief — the operating system running beneath all of them — became visible.

And once it was visible, it was challengeable.

"Is it true?" I asked. "Is your value really contingent on personally attributable, controllable performance?"

"The CEO promoted me because I built a team that delivered results she didn't expect. She didn't promote me because I personally checked every spreadsheet. She promoted me because I created something larger than myself." He paused. "My operating system hasn't caught up with my actual career."

The power of three

Why three clouds? Why not one, or five?

One cloud gives you a specific conflict. It is powerful, but it is local. You dissolve it and move on. You may not see the pattern that connects it to the next conflict, and the one after that.

Two clouds might reveal a connection, but two points define a line — you cannot be sure the line is real rather than coincidental.

Three clouds give you triangulation. Three different angles on your thinking system, each generated from different data (different LSI styles), all converging on the same core belief. When three independent clouds point to the same underlying assumption, you can be confident you have found something real.

Five or more clouds are possible but rarely necessary. In practice, three is the sweet spot — enough to triangulate, focused enough to work with.

The two brakes show you what your defensive system is protecting and how. The accelerator shows you what the defensive system is suppressing. Together, they reveal the core conflict: the tension between the security your current thinking provides and the satisfaction your development requires.

This is the Security–Satisfaction tension made personal and precise.

From three clouds to one practice

Once the core belief is visible, the work follows the same path as any dissolved cloud — but at a deeper level.

David's technical tactics addressed all three styles simultaneously, because all three were expressions of the same belief:

• He created a "development outcome" metric for his quarterly review, making people growth visible and measurable (dissolving Cloud 3's assumption that only task outcomes count)
• He proposed a process review with his team, inviting them to identify procedures that no longer served the work (dissolving Cloud 2's assumption that following conventions was the price of belonging)
• He established a delegation framework with clear quality criteria that his team co-designed, replacing personal verification with shared standards (dissolving Cloud 1's assumption that only his hands could ensure quality)

His adaptive work went deeper than any single cloud had taken him. The evolved belief was not about delegation or convention or task focus. It was about identity itself:

This belief did not replace the three individual insights from his earlier clouds. It integrated them. It was the belief beneath the beliefs — the operating system update that made all three tactical changes feel coherent rather than forced.

Practice: Your three clouds

If you have access to the Life Styles Inventory™, complete LSI 1 before reading further. The method works best with real data about your actual thinking patterns.

If you do not yet have access to LSI 1, you can still begin. Use honest self-reflection to identify:

1. Two defensive thinking patterns that cost you the most — behaviours driven by security, protection, or control. These are your brakes.
2. One constructive thinking pattern you most want to develop — a way of thinking driven by growth, connection, or meaningful contribution. This is your accelerator.

The LSI gives you precision. Self-reflection gives you a starting point. Either way, the method is the same.

Building your three clouds

For each of your three styles, follow the standard cloud-building process:

For each brake (security-based style to reduce):

1. D': Describe the behaviour this thinking style produces. What would someone see you doing? Make it observable, repeated, and positively phrased.
2. D: NOT D'.
3. B: What would NOT doing this behaviour give you? Go wide, then deep. Find the felt word.
4. C: What does this behaviour give you? Push past the presentable answer to the real protection. This is the security need.
5. A: What do B and C both serve?
6. Assumptions: Read each arrow. What must you believe for this logic to hold?
7. Challenge: Which assumptions are testable? Which are already false?

For the accelerator (satisfaction-based style to increase):

1. D': Describe your current behaviour — the pattern that prevents this style from developing. What do you do instead of thinking this way?
2. D: NOT D'.
3. B: What would developing this style give you?
4. C: What does your current pattern (not developing this style) give you? What would you lose?
5. A: What do B and C both serve?
6. Assumptions: What must you believe about why you cannot develop this style?
7. Challenge: Test those assumptions against evidence.

Triangulating

Once all three clouds are built, lay them side by side and ask:

• What assumptions appear in more than one cloud?
• What core belief would explain all three patterns simultaneously?
• If you could change one thing about how you think, what would dissolve all three clouds at once?

The answer to that last question is your core conflict. It is the deepest lever in your personal system — the one belief that, if dissolved, would unlock change across multiple dimensions of your thinking and behaviour.

Developing your integrated practice

Your tactics should address the core belief, not just the individual clouds. Ask:

• What one experiment could test the core assumption?
• What daily practice would reinforce the new belief across all three dimensions?
• How would you know, in six months, that the core belief had shifted?

Use the evidence journal from Chapter 12. Track changes across all three styles. The LSI can be retaken after a period of deliberate practice, giving you measurable evidence of shift.

What the three cloud method is not

It is not a replacement for the single-cloud work you have done throughout this book. Single clouds remain the right tool for specific, situational conflicts. The three cloud method is for systemic work — understanding the patterns that generate your conflicts, not just the conflicts themselves.

It is not a one-time exercise. Your thinking system evolves. The styles that dominate today may shift as you develop. Revisiting the three cloud method periodically — especially after significant life or career changes — keeps your development intentional.

And it is not something you do alone. The three cloud method benefits enormously from facilitation. A skilled facilitator can see connections between your three clouds that you, inside the system, cannot. This is where Level 2 Hosts and experienced practitioners become invaluable.

Closing

The Evaporating Cloud began as a tool for dissolving specific conflicts. The three cloud method turns it into something larger: a systematic approach to understanding and transforming your entire thinking system.

By choosing two brakes and one accelerator from your Life Styles Inventory™ results, you generate three clouds that triangulate your core conflict — the deepest belief holding your current pattern in place. That core belief, once visible, becomes workable. And working it changes not just one behaviour but the operating system that generates all your behaviours.

David's three clouds showed him that his perfectionism, his conventionality, and his task focus were not three separate problems. They were three expressions of one belief: that his value depended on visible, controllable, personally attributable performance. Dissolving that belief did not just free him to delegate. It freed him to lead.

The next chapter takes this further. The Life Styles Inventory™ 1 is a self-assessment — how you think you think. But how you think you think and how you actually behave are not always the same thing. The gap between them is where the next level of development lives.

That is the work of Chapter 15.

Your Thinking System — Level 3

Level 3 of YourThinkingCoach pathway takes your development deeper. Using the Life Styles Inventory™ and the three cloud method, you work your personal system with fellow practitioners who are doing the same. The book gives you the method. Level 3 is where you apply it to your circumplex.

Thinking Coach is Level 3 of YourThinkingCoach pathway — the entry point for anyone who wants to change how they think, lead, and work.

Explore Level 3 →

← Previous: Chapter 13: Facilitating for Others

→ Next: 🔍Chapter 15: The Gap

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