Chapter 7: Step 4 — Honouring What's Working: Benefits of D′ (C)

The Patterns That Refuse to Die

Robert Kegan likes to open with a riddle. Fourteen frogs are sitting on a log. Three of them decide to jump in. How many are left on the log?

Fourteen. Deciding to jump and actually jumping are not the same act — and the gap between them is where most of a life is spent.

Kegan and Lisa Lahey spent decades studying that gap. The finding they open their book with still stops me cold: when heart specialists tell their most at-risk patients that they will die unless they change how they eat, move, and smoke, only one in seven manages to change. Not because the other six don't want to live — they want it as much as anyone — but because something in them is pulling just as hard the other way.

Kegan tells the story of one of those patients: a man of fifty-eight, prescribed a medication he was meant to take every day for the rest of his life. He understood exactly why. He knew a stroke could kill him. The drug had no side effects and was covered by his insurance. Asked what the odds were that he'd still be taking it a year on, he looked at the interviewer as though the question were daft — a hundred percent, obviously. Why on earth wouldn't he?

A year later, he wasn't taking it. And when Kegan asked him — gently, and from an unfamiliar angle — what his worst feeling would be if he did take the drug every single day, something surfaced that the man had never once seen in himself. "If I have to take that damn drug every day," he said, "I'm going to feel like an old, sick man. Like my father's generation, sitting in a nursing home. I'm fifty-eight. I'm in the prime of my life. I'm not some half-dead man who has to take a pill to stay alive."

There it was. Not a man careless about whether he lived. A man protecting something — his sense of himself as vital, unfinished, not yet in decline — with such quiet force that it was overriding his will to survive. Sitting with it, he said the thing that names this entire chapter:

"You're showing me that in order not to feel like an old, sick man, I'm doing things that are likely to lead me to be a dead man."

He wasn't failing to take his medication. He was succeeding — brilliantly, invisibly — at protecting himself from an identity he couldn't bear. One foot hard on the accelerator: I want to live. One foot hard on the brake: I will not become that man. And the brake was winning.

This is the half of change almost everyone misses.

In Chapter 6, you named what change would give you. If you did the work, you have a B that animates you — a concrete picture of what you'd gain.

And yet, if you're like most people who reach this point, something still nags.

Because if B were enough on its own — if naming what you want were sufficient to move you — you would have changed already. The fact that you haven't, despite knowing what you'd gain, is not a failure of willpower. It's a signal.

The signal is this: your current behaviour is doing something for you. Something it is still doing right now — the foot pressed quietly on the brake. And until you can see what that is, no amount of B will move you.

That hidden benefit is C. This chapter is about finding it.

Kegan and Lahey have their own name for what stopped that man: an immunity to change — a hidden competing commitment running beneath the one he'd announced. Their way out is to name the big assumption underneath it and then test it. Ours runs differently. We surface C in full, and then — in Chapter 8 — we go up to the outcome both sides are really serving, A, and dissolve the conflict rather than test our way past it. But the discovery they lit up is exactly the one this chapter turns on: the behaviour you most want to change is protecting something you have never let yourself see.

Why C Is the Harder Half

Most people resist exploring C. There are good reasons for this.

C Exposes Vulnerability

David's real C wasn't "certainty." It was the version of me who stood back when he could have stepped in. That's painful to admit. It touches something deep — a fear of being the leader who failed by withholding.

Most C lists, when you go deep enough, arrive at something tender. Something you'd rather not see. This is exactly why people stay stuck: to avoid the C, they avoid the whole exploration.

It helps to name what's happening here. Brené Brown defines vulnerability as "uncertainty, risk, and emotional exposure" — and insists it is "not weakness" but "our most accurate measure of courage." What keeps us from it, she found, isn't fear itself but the armour we wear against it: the ways we defend and control so we're never caught exposed. Look again at David's first answers — certainty, control, nothing gets past me unchecked. That is armour. It's the sword he carries so that no one, least of all himself, sees him unsure.

And armour is always worn for security. Your C lives in that same place — the familiar, guarded ground that feels safe precisely because it's known. To name your true C, you have to set the sword down and look at what it was protecting. That lowering is the vulnerability — and by Brown's measure it isn't weakness at all, but the most accurate evidence of your courage.

C Challenges Self-Image

We like to think of ourselves as rational beings making free choices. Discovering that our behaviour has hidden benefits — benefits we've been pursuing unconsciously — challenges this image.

"I'm not the kind of leader who can't let go." Maybe not consciously. But if your behaviour consistently keeps the work inside your hands, part of you is keeping it there.

C Feels Like Making Excuses

"If I admit my behaviour has benefits, aren't I justifying staying stuck?"

No. You're understanding why you're stuck. There's a difference between explanation and justification. Explaining why David pulls the work back doesn't make pulling it back right. It makes change possible.

Surfacing C: David's Hidden Benefits

Kegan's patient was protecting his sense of being alive. David — the leader we've been following — was protecting something quieter, but no less tender. Let's return to him.

"David, we've explored what NOT taking the work back would give you. Now I need to ask a different question. What does taking it back give you? What do you get from your current approach?"

He shifted uncomfortably. "I mean… nothing good. That's why I want to change."

"I understand. But humour me. Pulling the work back has been with you for years. It's survived every attempt to change. If it gave you nothing, you'd have stopped doing it. So what does it give you?"

A long pause.

"Certainty, I suppose. I know exactly what's going out. I know it meets the standard."

"What does certainty give you?"

"Control. Nothing gets to the client — or to the board — that I haven't checked."

"And what does that control give you?"

Another pause, longer this time. "Safety, I think. If something's wrong with the work, at least I'll have seen it before anyone else does. I won't be surprised. I won't be ambushed."

We were getting somewhere. But there was more.

"What about the moment you actually reach in and take the work back? What does that act, specifically, give you?"

"Relief," he said immediately. Then he caught himself. "Which is strange, because it costs me my evening every time."

"Why would the relief matter more than the evening?"

"Because…" He stopped. "Because the alternative is sitting with the fact that something with my name on it is being finished by someone who might miss what I'd catch. And if they miss it, it lands on me. Worse — it lands on me having known I could have just done it myself."

"So what's the deeper benefit?"

"Protection. From being the leader whose team let something through. Protection from the version of me who stood back when he could have stepped in."

There it was. The benefit hiding beneath the behaviour.

C (Benefits of taking the work back):

• Certainty about what's going out
• Control over the quality and standard
• Minimised risk of being surprised
• Protection from someone else's miss landing on him
• Reassurance that he tried — that he didn't stand back
• Maintained identity as the one who delivers, the one who makes things work
• Protection of his reputation as a safe pair of hands
• Avoidance of difficult feedback conversations after the fact
• A continued sense of being needed and indispensable

Bringing B and C Together

By this point David had both lists in front of him — the B he'd built in Chapter 6, set against the C we had just surfaced.

B (Benefits of NOT taking the work back):

• Time and energy for strategic work
• A team that grows in capability and confidence
• Genuine ownership held by the people closest to the work
• Bandwidth to think beyond the immediate
• Scalability — a function that doesn't depend on me being inside every deliverable
• The credibility that comes from leaders who actually develop leaders
• Real trust, demonstrated rather than declared
• Sustainable leadership
• The kind of impact that outlasts me

Set beside his C — certainty, control, safety, being needed, the safe pair of hands — the two columns looked, at first, like a straight contradiction. Then David saw it differently.

"When I look at these side by side," David said slowly, "I see something I never saw before."

"What's that?"

"I want a team that can run without me — that's B. But I'm terrified that a team running without me means I'm no longer needed — that's C. The take-back isn't blocking the team's development by accident. It's blocking it on purpose. Because if they never quite finish without me, I never have to find out who I am when they don't need me."

This was the insight that changes everything. David wasn't failing to delegate. He was succeeding at protecting himself from his own redundancy — just as Kegan's patient was succeeding at protecting himself from becoming an old, sick man. His behaviour wasn't irrational. It was perfectly logical, given what he was quietly trying to protect.

And notice the shape of it, because it's the pattern beneath every cloud: B and C mirror each other. David wants a team that can run without him (B). He fears that a team running without him will prove he isn't needed (C). The benefit he seeks and the benefit he's guarding are the same underlying need — to matter — facing in opposite directions. He isn't torn between two goals. He's caught between two strategies for one goal.

"So here's my question," David said. "How do I get a team that can run without me without losing the role I have inside it? How do I get B without losing C?"

Hold on to that question. It's the doorway to A — and we'll walk through it in Chapter 8. But first, your C has to be real. Not the presentable version. The true one.

How to Surface a True C

Surfacing C requires patience and compassion. These questions help.

"What does D′ give you?"

The direct question. Simple, but often met with resistance.

"What would you lose if you stopped doing D′?"

Sometimes benefits are easier to see as potential losses. "What would you lose if you stopped taking the work back?" might unlock what "What do you get from taking it back?" cannot.

"Why has this pattern survived every attempt to change?"

This question respects the intelligence of the pattern. It's been with you for years. It's survived every commitment, every strategy, every coach. That survival signals value.

"What's the worst thing that could happen if you did D?"

This often reveals what D′ is protecting you from. David's worst case — being the leader who stood back when he could have stepped in — revealed what his take-back was defending against.

"If a friend were doing this, what need might you imagine it's meeting?"

Distance helps. It's easier to extend compassion and insight to others than to ourselves.

"What did this pattern once solve?"

Many C benefits made more sense in the past. David's take-back habit was forged in earlier roles where he genuinely was the most senior person who could catch the miss. The pattern that protected him then is now constraining him — but it began as a genuine solution.

The Trap: Staying Surface

Just as B can become a checklist, C can stay safely superficial.

"What does taking the work back give you?" — "Quality assurance." "What else?" — "Standards." "What else?" — "Reliability for the client."

This is C as a socially acceptable list. It's not wrong — these benefits exist. But it's not the real C. The real C hides beneath these presentable answers.

The test: Does your C list explain why you haven't changed? If your benefits are "quality assurance" and "standards," why wouldn't you simply find another way to maintain them — checklists, reviews, peer QA? The answer is that the real benefits go deeper. Push past the presentable layer. The C that keeps you stuck is usually the one you least want to admit.

What a Good C Looks Like

• Honest. It includes benefits you'd rather not admit. If your C list is entirely presentable, you haven't gone deep enough.
• Specific. "Safety" is vague. "Protection from being the leader who stood back when he could have stepped in" is specific. Specificity enables transformation.
• Felt. When you read it, you feel something — discomfort, recognition, perhaps compassion for yourself. A C list that leaves you unmoved hasn't touched the real benefits.
• Explanatory. It explains why you haven't changed. "Of course I haven't changed — look what my current behaviour gives me."
• Complete. It covers the full range, from practical ("certainty about what's going out") to psychological ("protection of my identity as the one who makes things work").

Case Study: Sarah's Hidden Benefits

Remember Sarah from the previous chapter? Her B was clear: voice, influence, recognition, modelling something different for the women coming up behind her. She knew exactly what she wanted from change.

And yet she stayed quiet. Meeting after meeting.

That's the test of whether C is doing its work — and Sarah's C was doing it powerfully.

C (Benefits of staying quiet and deferring):

• Harmony in the room
• No risk of being seen as difficult or political
• Protection from being wrong in front of senior people
• Preservation of the relationships that got her here
• Safety from the cost of disagreeing with the wrong person at the wrong time
• No exposure to challenge or pushback
• Maintained identity as the considered, measured one
• Belonging in the inner circle
• No risk of being the one who slowed things down

The surface C was "harmony." But we went deeper.

"What's the worst that could happen if you spoke up and held your ground?"

Sarah's response revealed her real C: "They'd reconsider whether I belong in the room. Right now I'm trusted. The moment I become the person who pushes back, I'm not just adding a view — I'm reshaping how they see me. And if they decide they prefer the old version of me, I lose the seat."

Her deepest benefit wasn't harmony. It was belonging in the room itself. She deferred not because she didn't have a view, but because being in the room mattered more than being heard in it. Speaking up risked the seat. And every strategy — preparing better, scripting interventions, briefing the CEO beforehand — had failed because all of them still carried that risk.

Her cloud mirrors David's exactly. Sarah wants a voice in the room (B); she fears that using it will cost her the seat (C). Voice and seat are the same need — to belong somewhere that matters — pulling in opposite directions. Like David, she isn't choosing between two goals. She's caught between two strategies for one.

Your Turn: Surface Your C

Now your turn.

1. What does your current behaviour give you? Start with the direct question.
2. What would you lose if you stopped? Sometimes loss is easier to see than gain.
3. Why has this pattern survived every attempt to change? Respect its intelligence.
4. What's the worst that could happen if you did D? This reveals what D′ protects you from.
5. What did this pattern once solve? Trace its origins.

Push past the presentable layer. The real C is usually the one you least want to admit. Then test it: does your C explain why you haven't changed? Does it make your stuckness make sense? Do you feel something when you read it?

Look for the mirror. Set your B (from Chapter 6) beside your C. Are they the same underlying need, facing in opposite directions — the benefit you seek and the benefit you're protecting?

Write both lists in full before you turn the page:

• B (Benefits of D): [from Chapter 6]
• C (Benefits of D′): [your new list]

The Question That Leads to A

You now have four of the five pieces of your cloud — D′, D, B, and C. What you don't yet have is the thing that reconciles them: the single outcome both B and C are ultimately serving.

Because David's B (a team that can run without him) and his C (still mattering to it) aren't really enemies. Neither are Sarah's voice and her seat. Each pair is two strategies reaching for one destination — and that destination is A.

That's the discovery Chapter 8 is for. Once you can see that B and C are both serving A, the question stops being which do I sacrifice? and becomes what new strategy might serve A while honouring both?

That question is where conflicts dissolve.

Support for this step

Surfacing C — the hidden benefits of your current behaviour — is the step most people resist. It asks you to see that the pattern you want to change is giving you something valuable, and the real C is usually the one you least want to admit. This is where the work gets tender, and where most people benefit from not doing it alone.

RIC — the Rapid Improvement Coach is an AI agent built specifically to support you through the process. RIC holds the space while you push past the presentable answers — quality, professionalism, thoroughness — toward the protection underneath. RIC asks what you would lose, what the worst case would be, why this pattern has survived every previous attempt to change. You choose how deep to go; RIC stays warm, stays patient, and does not judge what surfaces.

The Rising Above the Clouds course includes RIC, a discussion tab with the author, and membership of the Conflict Club.

Rising Above the Clouds - The Course