Chapter 11: Step 8 — Surfacing Options on C–D′

The first time Sarah looked at her cloud, it felt like a verdict.

The second time, on the train back from London the following Thursday, it felt like a question.

She had the pages on her lap, the cloud drawn in pencil so she could erase the arrows and redraw them. She read the C–D′ arrow aloud — the sentence connecting her need to know her contributions would land with her habit of rehearsing internally until the moment passed. A week ago she had read that same sentence and felt the truth of it land like a stone. Now she read it and found herself asking a different question.

Is that the only way to get certainty about how my contributions will land?

Every cloud feels like a prison while you believe its arrows are necessary. The moment you ask whether the arrow is necessary, the cloud becomes something else — a set of hypotheses you can test, one by one, until you find the one that gives.

For what follows, David's and Sarah's clouds sit alongside the method, because the method only really makes sense when you watch it work. Here is what they had built by the end of Chapter 8:

☁️

David's Cloud

A: Sustained leadership impact — a function that scales beyond me, led by someone the organisation continues to trust

B: A team that can run without me, bandwidth for strategic work, scalability, sustainable leadership, the kind of impact that outlasts me

(To achieve A, I need B)

D: NOT take back work after setting up delegation

(To have B, I want D)

A: Again, sustained leadership impact

C: Certainty about quality, control over the standard, protection of credibility, a clean track record the organisation trusts

(To achieve A, I need C)

D′: Take back work after setting up delegation

(To have C, I want D′)

The conflict: D and D′ cannot both be true at the same time.

☁️

Sarah's Cloud

A: Sustained effective impact in my leadership role — the standing to shape what this business decides, over time

B: Expertise informing decisions, a voice in the room, influence with the CEO and her peers, recognition for contribution

(To achieve A, I need B)

D: NOT stay quiet in leadership meetings and defer to whoever spoke last

(To have B, I want D)

A: Again, sustained effective impact in my leadership role

C: Belonging in the inner circle, the seat itself, protection from being seen as difficult, preserved relationships

(To achieve A, I need C)

D′: Stay quiet in leadership meetings and defer to whoever spoke last

(To have C, I want D′)

The conflict: D and D′ cannot both be true at the same time.

The arrows are not facts

Here is the move that changes everything.

The arrows in your cloud are not facts. They are assumptions.

Each arrow is a belief about necessity:

• A → B: “I must have these benefits to achieve my outcome.”
• A → C: “I must also have these benefits to achieve my outcome.”
• B → D: “I must use D to secure B.”
• C → D′: “I must use D′ to secure C.”

There is also a D↔D′ relation in the cloud, but it is not a necessity belief we test — it is built in by construction. D was defined as the negation of D′ back at Chapter 5, so the two cannot both be true at the same time. That is structural, not assumptive, and the chapter does not work it.

Every one of these arrows feels, in the moment, like an iron law. That is why the cloud has held for so long. It is not that you have been weak. It is that the logic has been invisible.

Beliefs are assumptions about how we think things are. Mandela, on leaving prison, spoke of two prisons — the physical walls with a release date, and the mental walls that had none unless he chose to set them free. Our mental traps are the worse of the two, because we cannot see the bars. David and Sarah now have a way to see theirs.

And here is the principle this chapter rests on: every cloud is dissolvable. Goldratt's foundational claim — and the experience of every Perry Approach Practitioner since — is that conflict is not ontological. It does not exist in how things are. It exists in how we are thinking about how things are. Every cloud is held together by assumptions; loosen the assumptions and the cloud dissolves.

This is why we say dissolve, not resolve. Resolving accepts the conflict as real and seeks a settlement within it. Dissolving says the conflict was never real — it was a structure built from erroneous assumptions, and once those loosen, the structure falls away.

The engine of dissolving is abductive inquiry — the creative move of asking what other way is there? The question itself opens the possibility space the assumptions had closed. Whether the first answer is good or not does not matter; the question has already done its work.

The lineage runs further back than TOC. Peirce, who coined the term abduction, placed it as the engine of all inquiry. Andersen (2024) traces the line from Peirce's synechism through to Goldratt's Theory of Constraints.

The work of this chapter is to ask that question of the right arrow, and to meet the assumptions the question loosens.

The leverage point

Four necessity arrows. Two of them hold the present in place — and they are where the leverage lives.

• C → D′ (this chapter): “In order to have C, I want D′.” Your current behaviour as the route to what C is protecting.
• A → C (next chapter): “In order to achieve A, I need C.” The deeper belief about what C is really for.

We start with C → D′ because it is usually the tightest arrow: over time the route (D′) becomes indistinguishable from the destination (C).

Two kinds of assumption

Not all assumptions do the same work. In the Perry Approach, we sort them into two categories — and almost every cloud worth bringing here has both.

Technical assumptions are claims of the form “this is the only way to deliver this.” They are means-end claims. They describe routes — the route, the way the practitioner has been seeing the path from need to behaviour. “I must personally check this to know it has been done properly.” “Approval requires the Director’s signature.” “If I do not catch the error, no-one will.” Technical assumptions respond to options. Show another credible route to the same end and the necessity claim loosens.

Adaptive assumptions are claims of the form “this is how things are.” They are ontological claims, often fused with identity. “A serious professional checks everything.” “I am the only person who can hold the quality line.” “The seat cannot survive dissent.” They feel like seeing rather than believing, which is why they are hardest to surface. Adaptive assumptions do not respond to options — they respond to a shift in how the person relates to what they thought was just the way things are.

A value, in this method, is not a separate category from a belief. A value is a belief that has become emotionally fused with identity. The cognitive content is still belief-shaped; the fusion is what makes it feel ontological. That is why the same surfacing work reaches both layers — and why the deeper assumptions tend to surface later in a brainstorm than the shallower ones.

Almost every cloud has both. The technical layer sits on top, defended by means-end logic; the adaptive layer sits underneath, defended by identity. The work of this chapter is the technical work. The adaptive work comes in Chapter 12. We start with the technical for a structural reason: technical work softens the adaptive ground. When you brainstorm credible options on C→D′ and the necessity claim loosens, three things happen at once. The possibility space opens, which loosens the absolute weight of the adaptive claim. The safety to examine what is underneath increases. And the adaptive assumption itself becomes visible — because the technical defences have been moved out of its way.

That is why we always start technical. Not because the technical work is more important, but because it is the route to the adaptive.

A simple sorting test. When you read the assumption back to yourself, ask which response would feel most accurate.

• “There is another way to do this.” — Technical.
• “That is just how things are.” — Adaptive.

If both feel accurate, the assumption is layered. Most persistent assumptions are. The technical layer surfaces first; the adaptive layer surfaces underneath. Name them both, and work the technical first.

A note on thinking modes

Three modes of reasoning are useful here, and most practitioners default to one without knowing the others are available.

• Deductive — if this assumption holds, what must follow? The mode of testing. Use it on technical assumptions.
• Abductive — what else could explain this? The mode of alternatives. The C→D′ work lives here.
• Inductive — what pattern is showing up across cases? The mode through which deeper patterns announce themselves over time.

Most practitioners get stuck in deductive mode and cannot find the leverage. The leverage usually appears abductively, after deductive testing has done its work.

Always start with C → D′

If you only remember one thing from this step, remember this: start with C → D′.

The C → D′ question

The question to ask on C→D′ is not the general one — what must be true for this arrow to hold? It is sharper than that.

What options are there to deliver C without D′?

There is only one assumption under test on this arrow: “I must use D′ to meet C” — the claim that C can only be delivered by D′. Everything in this step serves to test it.

These options are technical solutions or tactics — practical alternatives that prove there is another way to meet C. There are always options. The work is to find them.

This is an abductive move. You are not testing the arrow head-on. You are searching for alternative routes to the same C. You do not have to argue the claim down — each credible option you find does that for you.

List options without editing. Some will be obvious. Some will feel uncomfortable. Some you will dismiss in the same breath you write them. Write them down anyway. The ones you dismiss fastest are usually the ones standing closest to the claim under test.

Aim for at least six or seven options.

David's C → D′

Here is David brainstorming options for delivering C without D′ — certainty about quality, protection of credibility, a track record the organisation trusts — without taking back work after setting up delegation.

1. Review only the final deliverable, not the work in progress.
2. Set explicit quality criteria the team applies before the work reaches him.
3. Peer review within the team before delivery.
4. Selective review by risk level — check the high-stakes pieces, release the rest.
5. Coach the team to develop their own quality instinct over time.
6. Step back entirely and let the function deliver without his hands on it.
7. Hand the quality line to someone else — a deputy, a quality lead.

The C→D′ arrow buckled.

It did not buckle because the options were necessarily good. Several would need work before they could deliver C reliably; the chapters ahead will do that work. It buckled because the existence of credible options — even imperfect ones — broke the necessity claim that D′ was the only route. The conviction loosened.

Sarah's C → D′

Sarah brainstormed options for delivering C — belonging in the inner circle, the seat itself, preserved relationships — without staying quiet and deferring.

1. Frame contributions as questions rather than direct challenges.
2. Build alliances before meetings, so the concern is shared rather than hers alone.
3. Acknowledge others’ points before adding her own.
4. Contribute early enough to shape the discussion, not late enough to derail it.
5. Frame concerns around shared outcomes rather than problems.
6. Lead with data and evidence rather than opinion.
7. Connect each concern to the objectives everyone in the room cares about.
8. Circulate a written perspective before the meeting, so her thinking is in the room before she is.
9. Voice a small, low-stakes disagreement and see how the room responds.
10. Name it out loud when she notices the room converging too quickly.
11. Ask the leadership team to adopt a devil's-advocate norm, so challenge is expected of everyone, not risked by her alone.

The C→D′ arrow buckled.

Sarah's C→D′ buckled the same way David's did. The arrow had felt like an iron law — that protecting the seat meant staying quiet. Eleven credible alternatives later, that necessity no longer held. The early ones came easily, because they were the comfortable ones — ways to contribute while staying safe. It was only when she pushed past them that the riskier alternatives surfaced: the ones that asked her to be seen rather than merely careful. She very nearly did not write those last few down. As with David, it did not matter that the options still needed work; several would. What mattered was that other routes to C now existed, and the conviction that D′ was the only one loosened its grip.

A note on AI and the abductive move

The abductive move — what other way is there? — is where AI is genuinely transformational, more than at almost any other point in the work.

A practitioner brainstorming alone can usually produce six or seven options before they run out of imagination, and those options tend to be shaped by the same closed possibility space that built the cloud in the first place. A team produces more, but a team is still bounded by its shared experience and culture. A large language model is different in kind. Asking an LLM for options is like inviting a million opinions into the room — not because it is wise in the way a person is, but because it has read across a vast range of how others have faced similar conflicts and the routes they found through them. It is access to collective wisdom at a scale no individual or team can match.

That changes the work. The bottleneck on the C→D′ brainstorm used to be generation — finding enough options to push past the first four or five. With AI, generation is effectively unlimited. The bottleneck shifts to selection — recognising which options fit your context, your constraints, your people, your moment.

That selection is the human work, and it cannot be delegated. The AI does not know what fits where you stand. The AI does not feel the tightening when a particular option lands on the assumption beneath. You do. The AI opens the possibility space; you do the discerning. The work of the practitioner is not diminished by AI — it is sharpened to its proper task.

Selecting options that dissolve the cloud

Generating options is the first half of the work on C→D′. Selecting from them is the second.

Stay wide while you generate. Do not discard. Selection is a separate move and it happens after the abductive work has done its loosening.

If we find an option that replaces D′ and still delivers C, the conflict between D and D′ dissolves. The either/or is gone, because a third path now exists. But the cloud as a whole only dissolves if that third path also delivers B. The cloud has two needs at the top — B and C — and both must be met for the work to be done. An option that delivers C but not B has not dissolved the cloud; it has only shifted it. The conflict between D and D′ is gone, but the gap between where we are and the outcome we wanted is still there.

The first selection criterion is therefore: does this option meet the B interests?

But — and this matters — do not discard options that fail this test. If an option would deliver C but does not meet B as currently written, ask the second abductive question:

What injection would make this option meet B as well?

An injection is an additional element — a capability, a structure, a sequence, a piece of context — that when added to the option transforms it from a partial solution into a full one. David's option of stepping back entirely fails B on its own. With the injection "build team capability first over the next nine months" it could meet B. Sarah's option of framing every contribution as a question protects the seat but may not register as real influence — C without B. With the injection “pair the question with a clear recommendation once the room is with her” it could hold both.

This is a second abductive move, and it is where many cloud dissolutions actually live. The option that looked discardable is often the one that opens the cleanest path — once the right injection is named. Keep the option, name the injection, and treat the pair as a single candidate for later selection.

There is a second selection criterion as well, which we will come to after the adaptive work in the next chapter: does the option align with the new A→C belief that the adaptive shift produces? The adaptive work expands the A→C belief — broadening what C can include, or how C relates to A. That expansion changes which options now fit. An option that seemed marginal under the original A→C may align cleanly with the expanded one; another may fall away. You cannot apply this second criterion until the adaptive work has been done. That is part of why the technical work comes first — and part of why we keep options wide here.

For now, on the technical side: stay wide, ask the B question, and where B is not met, ask the injection question. The options that survive — directly or with a named injection — are the candidates the next chapter will return to.

A → C belongs to the next stage

You may already feel the pull of the A→C arrow — the claim that your current benefits are genuinely required to reach your outcome. That is the next level of the work, and it belongs to the chapter that follows this one. If it pulls at you here, note what surfaces, then set it aside. The C→D′ loosening you have done is the foundation that work depends on.

When the options are not surfacing yet

There are always options — if C can be met at all, it can be met by more than one route. So when nothing surfaces, you have not found them yet; you have not run out. Usually the cloud needs sharpening (take it back to Chapters 4 and 6–8), or you stopped at the first three or four options and need to push further. If it still holds, do not push harder alone — bring in a Thinking Partner.

The Role of a Thinking Partner

You can do this step alone — the book is written so that you can. But if you can do it with a Thinking Partner, do. A good one does three things you cannot easily do for yourself.

They widen the options. Brainstorming alone, you stay inside the same possibility space that built the cloud; a second mind brings routes you would not have reached on your own.

They notice the tightening. When you dismiss an option too fast, something changes — the pause lengthens, the sentence slows. A good Thinking Partner notices that and stays there. You may not.

They do not solve. The temptation when watching someone resist an option is to relieve the discomfort by offering an answer. A good Thinking Partner does not. They hold the silence long enough for you to stay with what you have just said.

Why seeing is not enough — yet

You might expect that simply naming the assumptions would set you free. It rarely does.

If it were that simple, you would already have changed.

Those assumptions exist for good reasons. They were built from past experience, from genuine fears, from needs that once went unmet. They have protected something real. If we dismiss them, they will go underground and continue to run the conflict from there.

The method therefore asks something more careful. Meet each assumption with respect. Understand what it has been protecting. Then, in the chapters ahead, test whether the belief still fits the life you are trying to live now.

That adaptive work belongs to the next chapter.

Practice: Surfacing your options

Give your cloud some unhurried time. The real alternatives rarely surface in the first few minutes.

Work through C→D′ first. Brainstorm at least six or seven options for delivering C without D′. Each credible option that could deliver C without D′ weakens the one claim under test — “I must use D′ to meet C.”

Push past the first four or five — the early ones tend to be sophisticated versions of D′, and the real alternatives come later. If something adaptive begins to show — a belief about who you are, not just about the route — simply set it aside for the next chapter.

Closing

Your cloud is now more than a map. It is a map with a marked leverage point.

You have started where the leverage almost always lives — on C→D′ — and asked the abductive question: what options are there to deliver C without D′? The options you generated are themselves the proof that another way exists; they are technical solutions and tactics, and they are the material the next chapter builds on. Where C→D′ loosened and you have at least one option that could deliver both B and C — directly or with the right injection — you have your leverage. The deeper A→C work belongs to the next chapter, not to this one.

That is what a buckled arrow feels like. Not a solution. A loosening.

You do not yet have a plan. That is deliberate. Tactics built before the assumption is named are usually sophisticated versions of the current pattern. Tactics built after are different in kind.

That is the work of the next chapter.

What's Next

In Chapter 12, you'll do the adaptive work — exploring the A→C arrow, the second of the two arrows of inertia. This chapter worked C→D′; the next chapter works A→C, in that order. It is the deeper belief about what you need to achieve your outcome that keeps the old pattern in place even after the technical options have loosened C→D′. The technical solutions live here in this chapter; the adaptive shift is what comes next. Everything you need is in the next chapter. You can work through it on your own, at your own pace.