Category: Contemplative Practice

A leader comes back changed to a role built for the person they were before. The most senior leader is also the one who can build what receives that change, for themselves and for the people below them who come back changed too.

Chapter 22 named what a leader recognises in themselves; the receiving community has to be ready to hold that change.

What’s left when the frameworks fall away is the capacity to notice. This is the close of the arc: separation in chapter 1, dissolution in chapter 11, recognition in chapter 22, and now reception.

What reception actually is

A leader goes through separation and dissolution, then comes back to a role built for the person they were before. The leader has changed. The role, expectations, and surrounding system haven’t. Unless the organisation can receive what changed, the people who changed tend to slide back into their old roles or leave.

Reception is what the community does to take the changed person in.

NUMMI (New United Motor Manufacturing), the Toyota/GM joint venture in Fremont, did this on the factory floor in 1984, as recorded in This American Life episode 561 “NUMMI 2015” and in the company’s own Team Member Handbook. Toyota flew the unionised Fremont workers⁠—the same workers GM had reputedly written off as the country’s worst automobile workforce⁠—to Japan in groups of 30 in spring 1984. They worked alongside Toyota production workers at Toyota City for two weeks each. They saw a different way of working: workers stopping the line when something was wrong, workers being asked what they would improve, workers being helped rather than yelled at when they got behind. John Shook, the first non-Japanese employee at Toyota City and one of the architects of the NUMMI training, described how the first group’s two weeks ended: a sushi party where both sides wept openly, with grizzled union veterans of 30 years on the plant floor hugging their Japanese counterparts in tears.

Sending people through an immersion was the beginning; NUMMI still had to build a workplace where they could act on what they had learned. At NUMMI that building was management’s work. In your organisation it’s yours, and the people below you who change will need it as much as you do.

NUMMI’s reception

The Team Member Handbook NUMMI gave its workers opened with a personal welcome letter from Tatsuro Toyoda, the company’s president, framing NUMMI as the union of proven management methods with a first-rate production workforce. The handbook defined the Team Leader role as teacher and improvement coordinator. It made mutual trust a recurring theme. In the same document that set out the policies workers would follow, NUMMI named its commitments to them⁠—fair wages, benefits, employee development, and continuous employment⁠—in plain language.

NUMMI put money behind its commitment to its employees. Its Reserve Fund Plan opened with the goal of making every effort to avoid layoffs. Once a worker was past the evaluation period, NUMMI paid 10 cents for every hour worked, up to 40 a week (about 32 cents in 2026 dollars), into a fund in their name, to draw on within set limits if layoffs became unavoidable, or to take in full on leaving the company.

The dark mirror: the reception that failed

The This American Life episode also covered GM’s decades-long struggle to spread NUMMI’s lessons across the rest of the company. GM intended to learn. It sent 16 rising stars⁠—the “NUMMI commandos”⁠—to help start NUMMI and learn the Toyota Production System. Steve Bera, one of them, recalled the energy: they were ready and fired up, convinced they were going to do this and change the world.

Despite their study and passion, GM had made no place for what they had learned. Bera recalled that nobody at GM ever came back to the 16 of them to ask what the secret sauce was, or how the company might use it to its advantage. He quit after two years.

The Van Nuys experiment was the first serious attempt to replicate NUMMI at another GM plant, and it failed. Ernie Schaefer, the plant manager whose account chapter 3 quotes, came to locate the cause in what wasn’t there: you could see plenty that was different on the factory floor, but the one thing you couldn’t see was the system holding the NUMMI plant up, and at the time nobody grasped how large that system was.

GM plants installed andon cords (a rope along the line that any worker could pull to call a team leader, stopping the line if the problem couldn’t be fixed quickly) without the conditions that gave them meaning at NUMMI. Frank Langfitt, the episode’s narrator, noted that workers at some plants got yelled at for pulling them, and a few plants cut the cords down altogether.

The commandos had gone through the immersion and were ready to work differently. GM had installed visible parts of the system while leaving the system around them intact. The change came late: it was 15 years before GM took NUMMI’s lessons seriously, and it spent the next ten slowly putting them in place. In 2009, after the 2008 recession wrecked the car market, GM went bankrupt. Mark Hogan, one of the commandos, thought that if GM had brought the system in across the board in the late 1980s, it might well have avoided bankruptcy. Toyota had taken the title of world’s largest automaker from GM the year before, and the lesson cut both ways: at a 2010 congressional hearing on Toyota’s sudden-acceleration problems, its CEO Akio Toyoda said, “We pursued growth over the speed at which we are able to develop our people and our organization.”

A leader can do the recognition work, build the capacity to hold their paradigm as object, and still return to an unchanged context. The senior team, board, and investors may continue to reward the old role.

The same story in software

Software has its own GM story, and I’ve worked inside it. A product group learns to work in cross-functional teams that take a piece of work from idea to customer, while the rest of the business stays organised by function: work split by specialty, and managers planning how fully each skill is used. Org Topologies, which chapter 1 named as one of the most serious attempts at the redesign, calls the first arrangement a Delivery Topology and the second a Resource Topology. Its authors write that where the work needs learning and adapting, a Resource Topology “fragments responsibility, slows down feedback, and amplifies coordination overhead.”

As I said my goodbyes on one engagement, one person shared not how it had gone but their worry about whether it would hold. The teams had been through two big improvements to their operating model in a short time, both of which I had supported. Another change was coming, one I expected to pull things back, and they said a third so soon would be brutal; they worried about staff retention. Someone else had already named what sat underneath: the product and the people were in a much better spot, but the rest of the company and its history wanted to fight the change and reject it, and the business was the last gear to turn. The people in product and technology had changed, but they didn’t expect the organisation to support them.

The individual leader’s change stands a far better chance in an organisation that can do what NUMMI did from the start and GM took 15 years to begin: distribute authority and share information. In a software organisation that looks like a team that can stop a release without asking, and a backlog whose ordering everyone can see and question. The job is to build an organisation where sound judgement doesn’t depend on one changed leader staying in place.

Leaders today

The closest analogue to NUMMI’s trip might be a retreat, a coaching engagement of sufficient depth, a sabbatical with the right structure, or a small group that meets for years and holds the slow work between sessions.

The analogue needs a receiving community on the other side. Chapter 22 named four kinds of company: a coach who has walked their own version of the passage, a peer walking similar territory, a witness who knows you outside the role, and a community of others doing related work. These relationships give the change somewhere to live beyond the leader’s interior.

A leader returning from the analogue needs support other people can read and act on: written intent that guides decisions when the leader isn’t there, or a policy that signals long-term commitment when next quarter’s numbers get hard.

You needn’t wait for all four to assemble. Build one artefact by Monday from what the book has already given you. Run the chapter 17 intent protocol on one category of decision, or set and hold the chapter 16 limit on work in progress (WIP) on one team. Or, for one reversible, low-cost kind of decision, move chapter 18’s approval threshold one notch, and leave legal, safety, and regulatory approvals where they are.

None of it was wasted

Steve March, my Alētheia teacher, put the question to me on the call chapter 2 described, in May 2026. What if none of it was wasted?

The framework you were certified in and taught as good practice, on the promise that installing it wholesale would deliver the results it got somewhere else. The transformations you led that didn’t take. Chapter 1 has mine: years of teaching teams good practice, then watching it give way every time a fixed date came due, with no lever I could pull on the date itself.

Some choices were wrong. Some transformations failed. Yet the years inside those frameworks taught you how a framework feels from within, how identity gathers around it, and what happens when reality no longer fits. You couldn’t have learned that by skipping ahead.

The leader’s previous paradigm got them here, and respect for that history is part of moving forward. A leader who can honour what the old paradigm made possible can recognise when the context it worked for has shifted, and set it down without having to condemn the person who once needed it.

What’s left

NUMMI’s handbook carried one more thing: a framed aphorism, attributed to no one, set just before the section on the savings plan.

“If you accept an explanation without question you may have lost the chance to understand. You must learn to say ‘I don’t understand.’ In effect, this means breaking away from common assumptions.”

It asked every worker on the line for the discipline a returning leader most needs. Someone says I don’t understand, the explanation stays open, and the decision can change. A leader who can do that can govern an AI without pretending to know what they can’t know. In my own practice, the meditation cushion asks for the same discipline: loosen my grip on the explanation and come back to what I can see.

When the reception is built and the artefacts are in place, what remains is the capacity they were meant to protect. Steve March named it for me on that call in May: just this. As I understand it, action arises from contact, before a separate self steps back to choose among its accounts of what is happening.

In chapter 13’s pattern recognition, a stored pattern fires fast, and it’s only as good as the regular environment that trained it; just this stays in contact until the situation shows itself, which is how a leader meets an irregular environment before any pattern fits it.

You stay with what you can’t yet say, and you keep staying, and at some point it shifts and shows you the next step. Eugene Gendlin, the author of Focusing-Oriented Psychotherapy, called that carrying forward. Contact with reality is more reliable than abstraction about reality. Plans and frameworks can help us stay in contact and make sense of what we find, but they can’t replace contact. Stay with what is actually happening now, between these people, under these constraints, in this body or system.

Contact with reality is more reliable than abstraction about reality. Plans and frameworks can help us stay in contact and make sense of what we find, but they can’t replace contact.

There is only the practice⁠—in the project retrospective, on the meditation cushion, in the chalk circle on the factory floor, with your kid, with your dying parent, with your customer, with your code⁠—of noticing when you have slipped from contact into framework, and coming back.

Over a career, that return turns every framework the leader holds from an identity into a tool. When defensive patterns step back, the qualities of Self named in Richard Schwartz’s Internal Family Systems model⁠—curiosity, calm, clarity, courage among them⁠—become available. They weren’t installed as virtues. They were there when the protectors released their grip.

Notice when contact slips into framework. Come back. The community of practice forms slowly over years.

If this work is live for you and we haven’t yet spoken, schedule a 30-minute call at hi.chrisgagne.com. I’d love to hear from you. I am one practitioner among others doing this work. Some of the practitioners I would refer leaders to are people I have studied with or worked alongside.

Thank you for reading. Thank you for the comments, the questions, the disagreements, the moments where you wrote to say that something hit home. The book is better for them, and I’ll keep improving it as I learn.

Just this.

Going upstream

I draw on two primary sources on NUMMI, read against each other. The reception artefacts are drawn straight from the Team Member Handbook, the document New United Motor Manufacturing issued to its Fremont team members in 1984: the Toyoda welcome letter, the Team Leader role defined as teacher, the Reserve Fund Plan on page 58, and the framed aphorism before the Savings Plan section about learning to say “I don’t understand.” The dark mirror, GM’s decades-long struggle to spread what NUMMI proved, comes from This American Life, episode 561, “NUMMI 2015”, which carries what happened when GM installed andon cords, the NUMMI commandos, Steve Bera’s, Ernie Schaefer’s and Mark Hogan’s accounts, and Akio Toyoda’s 2010 testimony on pursuing growth faster than Toyota could develop its people. Where I quote or paraphrase either, I am reporting what the source itself records, not my memory of the story.

Resource Topology and Delivery Topology are Alexey Krivitsky, Craig Larman, and Roland Flemm’s terms, and the quoted line on what the first does to work that has to keep learning is from their 10X Org: A Manager’s Guide to Elevating Business Performance with People and AI. Ways to build these conditions in software organisations come from it and from Craig Larman and Bas Vodde’s Large-Scale Scrum: More with LeSS.

“Carrying forward”⁠—staying with what you can’t yet say until it shifts and shows the next step⁠—is Eugene Gendlin’s, discussed in his essay “Process Generates Structures: Structures Alone Don’t Generate Process” and running underneath Focusing-Oriented Psychotherapy. The qualities that surface when the protectors unblend⁠—curiosity, calm, clarity, courage⁠—are named that way by Richard Schwartz in No Bad Parts: Healing Trauma and Restoring Wholeness with the Internal Family Systems Model. “Just this” is Steve March’s: he offered it on a call I had with him in May, with the names it carries in Zen (appropriate response) and Tibetan Buddhism (self-arising wisdom). I use it as a lay practitioner reporting what the training points at, not as a teacher of it. And Steve March’s question⁠—what if none of it was wasted—came from that same call, not from a page; I record it here as his, gratefully.

Some book links here are Amazon affiliate links; if you buy through them I may earn a small commission, at no cost to you.

A new self has been forming, and you can’t see all of it from the inside. Recognising it takes company.

Chapter 21 asked you to notice and question assumptions that had been running you. Continuing that work calls for a different kind of company.

If you have come this far, something in you has been moving without your full knowledge.

Recognition here, unlike chapter 13’s expert pattern recognition, means noticing your own pattern before it produces the next decision, and pausing when a confident voice arrives⁠—from a peer, a board, an AI agent⁠—and asking whether it fits the situation.

This book follows the three stages of initiation Karla McLaren draws from the mythologist Michael Meade: separation, dissolution (his ordeal) and the return. Chapter 1 named separation and chapter 11 dissolution. I split the return in two: recognition here, reception in chapter 23. The 18 paradigm-axis chapters stand alone. It’s probably worth reading all 18 in time; but if two or three get you unstuck and looking at your beliefs more critically, that’s really the leap.

What you recognise about yourself

The leader at the recognition stage has walked through something they couldn’t have planned, and the walking produced a new self. Robert Kegan, the developmental psychologist, gives the mechanism in In Over Our Heads: “That which was subject becomes object to the next principle,” and the new principle “makes the prior principle into an element or tool of its system.” Put another way, what used to have you, you now have. The teenager who is their friends’ opinion of them grows into an adult who has an opinion about it, and can use it. And there is always a next one; as chapter 21 put it, we’re always subject to something.

For the leaders I’ve worked with, these recognitions have arrived in roughly this order.

Your career was built by a self that fit a context that has since changed. That self remains useful in the conditions that produced it, less useful in the conditions you now meet. What if none of it was wasted?

The patterns that built your career are still active. Mine is the fixer. In the same coaching recordings chapters 5 and 19 drew on, when someone says they don’t know if they can do this, I reassure them (“you’re doing wonderfully”) instead of meeting the uncertainty they have just put on the table. That move protects me from sitting in it at least as much as it protects them. It also solved a great many problems and built most of a career. The patterns aren’t enemies. They were protecting you from circumstances you no longer live in, and they keep acting as if those circumstances remain. They ease when someone sees them clearly with you, which willpower can’t do.

They were protecting you from circumstances you no longer live in.

What you were defending made sense. The kind of commitment an Immunity Map brings up (I have been committed to remaining the person without whom this couldn’t be done) is one version; the need to be right and the need to fit in with your peers are two other common ones. Each was sincerely held and suited the conditions that made it. Naming it doesn’t make it false. It means you can look at it instead of through it.

Not knowing has become bearable. The discomfort is still there, but you no longer have to end it straight away. When a confident voice arrives (your own, a colleague’s, an agent’s), you can hold off agreeing or disagreeing long enough to ask whether it fits the situation. Of the four, this is the one I see leaders notice last.

Ask the three questions one decision at a time: Which pole did I claim? Which pole did my behaviour show? Which pole did the situation require? The shift comes when the assumptions they surface are tested, with company, as chapter 21 describes.

What shows up when the patterns rest

What shows up when the patterns step back is what Richard Schwartz’s Internal Family Systems model calls the qualities of Self: curiosity, calm, clarity, courage, a subset of its eight Cs. Schwartz’s Self, capital S, is a different claim from the new self Kegan describes. Kegan’s self gets rebuilt at each passage; the qualities of Self are what each rebuilt self finds underneath when its patterns rest. The impulse to fix arrives, and it isn’t obeyed, and a genuine question becomes possible in the space where the fix would have gone. Personally, I spent years treating calm as a trait to install. The calm and clarity that show up in certain moments aren’t exceptional performances. They are what is left when the patterns rest.

What recognition needs

The leader at this stage doesn’t need another implementation framework (a sense-making one can still help). They need company.

An executive coach is one kind of company. The work also calls for a peer, a witness outside work, and a community.

The four kinds of company are my own grouping. The leaders I’ve watched move through recognition well had something close to all four; the ones I’ve watched stall usually had one or two and treated that as enough.

A coach who has walked their own version of the passage. A coach who has felt the dissolution of their own paradigm at some scale, worked through the trauma that the dissolution surfaced, and built the capacity to stay present while the same is happening to someone else. The coach’s lineage and training matter, and so does the supervision they themselves submit to. Without these, the coach can become an obstacle when the leader needs steady company.

A peer who has walked similar territory. This is a leader at a similar developmental edge, close enough in time and experience for straight talk about the work itself, but without the authority of a mentor or the rivalry of a competitor. Most senior leaders have had a peer like this in their career at some point; some have lost the relationship to time or circumstance and not replaced it. The peer relationship can’t be installed by HR. It is sought, recognised, and tended over years.

A witness who isn’t in the work. A friend, a partner, a long-standing relationship outside the professional context, whose presence reminds the leader that they aren’t their role. The witness doesn’t have to understand the work. The witness has to know the leader as someone other than the leader. Leaders often reach this stage and find that their relationships outside work have atrophied during the years of role-as-identity.

A community of others doing related work. This is often the smallest and hardest of the four to find: a group of leaders who are also trying to build the same sort of team you are, so you can talk about the slow work without translating it first. The group may be informal, but it has to be reachable when the next phase begins.

The recognition stage goes better with all four. Each missing kind of company puts more weight on the others. A leader with a coach and no peer has nobody who is in it at the same time; a leader with peers and no coach may have nobody who has already been through their own dissolution. The count is a way of finding where the exposure is, not a prediction about who makes it through.

On the coach who can stay in it

Dave Snowden, the complexity researcher behind the Cynefin framework, has critiqued industrial-level coaching that reduces developmental frameworks to platitudes divorced from complexity. Writing in “Stairways to Heaven?” (The Cynefin Co, 17 May 2022), he holds that while coaching helps in the organisational development process, “it is neither a necessary nor a sufficient condition to enable change”. I wholly agree and make a narrower claim: coaching can provide individual, relational company within the contemplative-presencing tradition I practise, but coaching alone can’t enable organisational change. Scaling business results still starts with the leader who owns the system doing their own inner work, which can’t be scaled or delegated. At the top, nobody above them can change the system for them.

A coach brings training and experience. Developmental frameworks and the ability to notice what’s happening in the body matter, along with trauma-informed training and contemplative practice. None of it substitutes for the coach who can stay present without flinching when paradigm-death begins in the work.

They refuse to shortcut. The leader will often want the shortcut. The coach who can hold it won’t provide it. I meet the shortcut constantly in how this work gets sold: promised speed, promised certainty, a method-oriented framework offered as sufficient.

They stay in steady contact with dissolution itself. The coach has been through their own version of the passage at sufficient depth that being in contact with someone else’s doesn’t destabilise their own foundation.

They know what they aren’t for. The coach can say I’m not the right coach for you when they aren’t.

Steve March, whose Alētheia training I have been in since 2023, builds on Reinhard Stelter’s A Guide to Third Generation Coaching to distinguish coaching that helps you solve or reframe a problem from coaching that can stay present while identity and certainty come loose. If you choose the first when you need the second, the passage gets managed instead of made: the problem gets reframed, the relief is real, and the thing that was dissolving reassembles. As March summarises Stelter, there are three generations of coaching method: the first, borrowed from sports, is about solving problems and reaching goals; the second opens new possibilities from resources the client already has; the third, process-oriented, works with whatever arises inside the conversation itself. March adds a fourth that brings what he calls unfolding depth. In my judgement⁠—extending March and Stelter⁠—paradigm-death coaching leans on the top two: process to work with what arises in the conversation, and presence to remain in contact with what is dissolving. Most coaches I’ve met are trained in the first two generations; fewer have training in the process-oriented third, fewer still in the presence-centric fourth. The training routes that reach the fourth vary⁠—contemplative-clinical traditions, depth-psychology programmes, certain developmental-coaching lineages⁠—but each trains the coach’s capacity to remain present, not only their command of method.

How to tell which coach can hold it

Look for these green flags.

A teacher and a lineage they can name. The lineage may be formal (a contemplative tradition, a clinical training programme, a depth-psychology school) or informal (a senior practitioner they have studied with over years). Either way, they can answer the question who taught you to do this? with a specific name and a relationship.

Ongoing supervision they submit to themselves. The work calls for an ongoing relationship with a teacher or peer who can witness the practitioner’s blind spots.

Their own continuing inner work. The distinction my lineage holds is between unfoldment (the slow growth of each quality of presence over years) and self-improvement (the acquisition of better skills, better techniques, better certifications). A trap I have been in myself is treating my own development as a self-improvement project: another certification, another method, another thing added. Ask what their most recent supervision changed in their own conduct, and listen for whether the answer is something they now do differently or something they now know.

Clarity about what the practitioner gets from the relationship. Price alone tells you little. Every coach gets something: a fee, new members for their community or movement, or the relationship itself. A low price doesn’t mean they want nothing. Ask what they get from working with you, and trust the one who answers plainly.

Willingness to say “I am not for you” and “you are not for me”. Both are real. A coach who can’t say either is selling something different from what this work calls for.

The red flags are the inverse.

Promises of transformation on a timeline. The work won’t follow an arbitrary timeline. It’s a complex unfolding process we can influence but not control, and a practitioner who promises a date isn’t doing this work.

Selling a method rather than meeting what’s here. Listen for whether they describe their steps or how they work with what you bring. A coach who runs the same method whatever arrives can’t stay with a passage nobody planned.

Marketing that sells self-improvement as the answer. Instant transformation. Become your best self. Unlock your potential. Steve March’s Alētheia training names the premise under it: a self-improvement project starts from a sense that something in you is lacking, and an economy runs on selling improvements against that lack. The idiom sells what contemplative practice spends lifetimes trying to undo.

The leader feels the practitioner needs them. A practitioner who needs the leader’s specific patronage to maintain their own practice is at risk of telling the leader what the leader wants to hear.

In my experience, these checks screen out most practitioners who can’t do this work. A poor match can slow the passage or stall it, so the leader can afford to be selective. Nobody in the coaching market enforces these checks, so the leader has to.

What’s yours to do now

Score the four as you actually have them today⁠—coach, peer, witness, community⁠—0 for absent, 1 for weak or lapsed, 2 for active. The witness and the peer are the ones I most often see at zero in leaders who have lived years inside the role. Don’t try to fix all four. Pick the lowest one you could strengthen this quarter and take one real step: the message you keep meaning to send, the friendship the role crowded out, the search for a coach who has walked their own version of the passage.

Contemplative-clinical traditions, depth-psychology programmes, and developmental-coaching lineages are starting points. One person may sometimes fill more than one role, but the target remains coach, peer, witness, and community.

Going upstream

The qualities that show up when the parts rest⁠—curiosity, calm, clarity, courage⁠—are four of the eight Cs of Self from Richard Schwartz’s No Bad Parts: Healing Trauma and Restoring Wholeness with the Internal Family Systems Model; the idea I lean on is Schwartz’s, that these aren’t virtues to install but what is already present underneath the protector activity. The hidden competing commitment surfaced by the Immunity Map is Robert Kegan and Lisa Laskow Lahey’s, from Immunity to Change. Chapter 21 walked the same move from subject to object in detail. The new-self mechanism, that what was subject becomes object to the next principle, is Robert Kegan’s, from In Over Our Heads.

The first three generations of coaching method are Reinhard Stelter’s, from A Guide to Third Generation Coaching, extended to a fourth generation—presence-centric depth coaching⁠—by Steve March in the Alētheia training I have been in since 2023; the framing that paradigm-death coaching leans on the top two generations is my extension of theirs, not theirs. Dave Snowden’s critique of industrial-scale developmental coaching is his “Stairways to Heaven?” post (The Cynefin Co, 17 May 2022).

For the rest, I draw more on lived practice than on citation. The four kinds of company and the coach-vetting checklist are drawn from watching leaders move through the passage well or stall, and from my own years inside the work, more than from any single book. The distinction between unfoldment and self-improvement is Steve March’s, from the Alētheia training.

I work with CTOs and CPOs at software companies with roughly 25–500 engineers, where the engineers are faster with AI and the business isn’t yet seeing the full value. The assumptions this chapter works on are often part of what’s delaying it, and I help leaders find and test their own. If it’s live for you, book a free 30-minute call at hi.chrisgagne.com and bring the one question that would make it worth your time. If you know a CTO or CPO in that spot, pass this chapter on. If you’d rather read on than talk, the newsletter goes on past chapter 23, monthly, at https://www.linkedin.com/newsletters/come-prepared-to-die-7472144387981062144/

Some book links here are Amazon affiliate links; if you buy through them I may earn a small commission, at no cost to you.

You can do all of this work and still come back to a role built for the person you were before. GM sent 16 of its rising stars to learn Toyota’s system at NUMMI. They were fired up, then waited for GM to deploy them; nobody asked what they’d learned, and one quit after two years at NUMMI. Chapter 23, the last in the book, shows what an organisation has to build so a changed leader doesn’t have to choose between fitting the old role again and leaving, and gives you one piece to build by Monday.

You’re surprised by your own pattern when it surfaces. The pattern was running you well before you saw it.

Chapter 20 ended on conflicts that persist because an assumption of your own makes the stated options seem exhaustive. The capacity beneath every axis is holding your own assumptions as object rather than being run by them.

A recurring pattern can look like a single event. The CTO who said no to the partnership for the third quarter in a row and then sat in the car afterwards wondering why. The VPE who promised the board a delivery date her team had missed twice before, and believed it this time too, then met the slip with real surprise. The senior manager who promoted the wrong person again, the same wrong choice they have been making for 15 years. Eventually, the leader notices that a pattern is repeating across the events.

The two poles

Pole A: subject to assumptions. The leader doesn’t experience their assumptions as assumptions; they experience them as the way the world is. The frame has them.

Pole B: holding assumptions as object. The leader can look at an assumption and hold it up to inspection. They can say that’s what I have been assuming about how this organisation needs to work, and I notice that assumption may not be fitting this situation. They have the frame.

The frame becomes a thing they have rather than a thing they are.

Robert Kegan, the Harvard developmental psychologist who has spent decades researching this change, names it as a structural shift in what one is subject to and what one can take as object. The Subject-Object Interview is the 90-minute interview Kegan, Lisa Lahey (his co-author on Immunity to Change) and their colleagues developed to assess where someone is on the developmental sequence; thousands of these interviews have now been run. As Kegan and Lahey describe it, greater complexity means being able to look at more of the thoughts and feelings that previously ran us. We’re always subject to something.

Where Pole A is right

Pole A is the structural default. Every leader is functionally subject to most of their assumptions most of the time. A working organisation depends on it.

The CFO acts on the assumption that the books should balance, without stopping to inspect it every Tuesday morning. Inspection takes time and effort, and when an assumption fits, the cost often isn’t worth paying.

The leader’s assumptions didn’t appear from nowhere. They were built over years, in response to specific conditions, by a self that was solving real problems. The CFO learned to be subject to the books-balance assumption because the early times in their career when the books didn’t balance were terrifying. The CTO learned to be subject to the team-must-trust-me assumption because the early times when the team didn’t trust them, the team didn’t ship. The assumptions are protective architecture. They got the leader here. Retroactive shame mistakes a protective response for a defect.

Where Pole B is right

Pole B is right when a recurring outcome gives the leader reason to question an assumption.

In Robert Kegan and Lisa Lahey’s analogy in Immunity to Change, an immune system is, most of the time, a beautiful thing: “an extraordinarily intelligent force that elegantly acts to protect us, to save our lives.” Every immunity to change can be read as an asset and a source of strength for the person carrying it. But immune systems can become part of the problem when they reject material the body needs. In Kegan and Lahey’s terms: “It is just making a mistake. It does not understand that it must alter its code.”

The same result keeps surfacing in different vocabularies, the same conversation keeps happening with different people, and the same diagnostic keeps appearing in the quarterly review. The leader’s behaviour under pressure keeps producing an outcome that surprises them.

The Immunity Map⁠—the four columns

Kegan and Lahey’s Immunity Map has four columns the leader works through in order. The worked example below is my own. Reading someone else’s map is useful; doing your own is the work.

Column 1: the improvement goal. What you genuinely, sincerely want to do differently. Mine: stay in contact with the people and the situation when the stakes rise, rather than collapsing into precision-as-defence. Let clarity serve. Hold accuracy without sharpness.

Column 2: the fearless inventory. The behaviours you do that work against the column-1 goal. Not what you do once in a while when you’re tired. What you do reliably. Mine: tighten under pressure. Sharpen the framing when I should soften the contact. Overshoot the audience with urgency that was meant for myself. Solution-shape a conversation that was asking for a slower kind of listening. Run certainty out ahead of what I have actually checked.

Column 3: the hidden competing commitment. What you sincerely commit to that requires the column-2 behaviours. Mine: to remain credible by being correct. To prevent exposure through precision. To make the situation safe by knowing more than everyone in it. The column-1 goal asks for soft contact; the column-3 commitment requires precision as armour. Both are running in the same body at the same time.

Column 4: the big assumptions. The assumptions that sustain the column-3 commitments. Mine: I am only safe when I am correct. If I am not precise, something will collapse. They won’t hold me if I am uncertain in front of them. As Kegan and Lahey put it: “We call them ‘big assumptions’ because they are not currently viewed as ‘assumptions’ at all. Rather, they are uncritically taken as true.”

The exercise works when the leader can put all four columns on one page and see the assumption that links them. My column-2 behaviours do exactly what column 3 needs them to do. As Kegan and Lahey insist, the map isn’t exposing an insincere commitment behind the real one. The heart patient genuinely wants to keep living even as he reaches for another cigarette; change fails to happen because we mean both things.

What runs after the map⁠—the continuous test

Kegan and Lahey’s tests are safe, modest experiments, run to get information rather than to get better. Kegan and Lahey note that as self-observation improves, tests start to happen in the moment; my own practice makes that deliberate and continuous: the same test, run each time the pattern starts.

After the Immunity Map is built, the leader doesn’t now know their assumption and move on. The assumption is still operating. My own continuous test is small and specific: in conversations where I feel the precision-tightening start, hold one breath of contact before responding. The column-1 goal becomes the action; the column-3 commitment surfaces in the felt resistance to softening. The felt resistance is half the data; the other half is external: what actually happened when you softened? Log both.

Repeated tests are what make the move from subject to object hold. Without them, the assumption tends to run the leader again.

The chapter’s own trap⁠—subject-object duality

If the leader treats holding assumptions as object as the high state and being subject to assumptions as the low state, they can start grading themselves against the binary. It shows up as a journal that grades every meeting against the binary, which is self-attack in developmental vocabulary. The frame has closed around them again, now through the demand to escape every frame.

The move from subject to object is a capacity to use when the situation calls for it.

Go back to the CTO in the car. What changes isn’t the partnership decision; it is that the question why do I keep saying no to this becomes available to ask, and the next call can be made on its merits rather than on the rule underneath it. The capacity lasts even as the assumptions change. I doubt the paradigm that fits today will still fit in 18 months. A leader who can take it as object can see that and adjust; a leader who has made one way of seeing part of their identity is stuck.

In decisions

At Pole A, the leader experiences the surprise as a thing happening to them. They name the situation as the cause without questioning what they assumed.

At Pole B, they can ask what their own assumptions contributed. They can say I am noticing the same anxiety I noticed the last three times this came up, and the anxiety is the information. They can sit with the discomfort long enough to inspect the assumption.

When a decision fails and the same failure has come before, there are two choices close to hand: defend the decision, or ask what assumption made it look right at the time. I have made both, sometimes in the same meeting. Questioning the assumption can mean discovering you were wrong.

Put one recurring pattern in front of your CEO. Use several incidents where the CEO’s response surprised you by repeating itself, rather than a single incident. Anchor it in shared work: one specific decision you were both inside, with the CEO’s account asked for first⁠—what were you trying to do there?—before you offer what you saw. The four-column map from Kegan and Lahey is your guide, not your script. Better still, build your own first two columns on the same decision and put them beside the CEO’s; chapter 18’s sticky-note exercise is the pattern: each of you holds the pen on your own rows, then you compare. Whether the CEO can hear it depends on the relationship. If the relationship is there, I suspect this is the most consequential conversation available to you. If it isn’t, start with a less charged axis and build toward this one. If the CEO declines the conversation altogether, that is information, not resistance to overcome. The offer stands.

The sentence your CEO can carry to the board: “I’ve made [the same call on X] [N] times with the same result; I’ve asked [two colleagues] to challenge it, and next meeting I’ll report what I tried instead and what happened.”

The diagnostic

• Take the last time you were genuinely surprised by your own behaviour, when afterwards you sat in the car or stared at the screen and wondered what just happened. Walk through the moment and ask: what assumption was operating in me right before that? Sit with it long enough to put the assumption into words. Don’t force it; the assumption is unfamiliar to you because you have been subject to it.
• Choose one assumption you can name about how your team or organisation has to work. Write it as a sentence. Now design one safe, modest behavioural test where you act against it this week. The point isn’t to disprove the assumption. Record what it costs you to act against it and what actually happens.
• Notice what arrives in you when you read this chapter. Tightening might mean the argument fits, or overreaches, or is simply unfamiliar, or that an assumption is defending itself. Which one is a question to test against evidence, not to settle by the feeling.

These questions need time you may not have planned to give them.

A team-based exercise

Walk the Immunity Map once, on yourself, before you try it with anyone else.

Pick a column-1 goal: something you genuinely want to do differently in your leadership and haven’t been able to do, despite trying. Run the four-witness check from chapter 2’s exercise before you lock it⁠—one question, four people who know you⁠—because they can name goals and effects your own protective habits leave out. Build the columns. Take an hour or two. In my experience column 2 is easy and uncomfortable, column 3 is the one that stings, and column 4 tends to arrive last.

Don’t share the map with your team yet. Sit with it for a week. Watch your own behaviour against the columns and notice when the column-3 commitment is operating. The continuous test starts here.

When the team learning is ready⁠—Kegan and Lahey found it made a crucial difference when leaders went first, as visible about their own immunity as they were asking their teams to be⁠—share the map with two people who have permission to push back. The work after that is collective, and slower than this chapter can describe.

Going upstream

Start with: Kegan, In Over Our Heads: the developmental theory the immunity work rests on, which names the move from subject to object, and the Subject-Object Interview that assesses it. Kegan and Lahey, Immunity to Change: the Immunity Map and the case studies. The continuous test above is my practice, built on their in-the-moment tests.

Further reading: Meadows, Thinking in Systems: on transcending paradigms at the top of her leverage-points hierarchy.

Go deeper: Garvey Berger, Changing on the Job and Unlocking Leadership Mindtraps: the same ideas, written for working leaders. Heifetz, Leadership Without Easy Answers and The Practice of Adaptive Leadership: the adaptive-versus-technical distinction the developmental work rests on.

I work with CTOs and CPOs at software companies with roughly 25–500 engineers, where the engineers are faster with AI and the business isn’t yet seeing the full value. The assumptions this chapter works on are often part of what’s delaying it, and I help leaders find and test their own. If it’s live for you, book a free 30-minute call at hi.chrisgagne.com and bring the one question that would make it worth your time. If you know a CTO or CPO in that spot, pass this chapter on. If you’d rather read on than talk, the newsletter goes on past chapter 23, monthly, at https://www.linkedin.com/newsletters/come-prepared-to-die-7472144387981062144/

Some book links here are Amazon affiliate links; if you buy through them I may earn a small commission, at no cost to you.

An old pattern can keep running after a paradigm dies, alongside the temptation to mistake reading about the work for doing it. In chapter 22 you work through the self-recognition that follows, and score the company that work needs.

Think of a time you handed your judgement to a confident voice: the CEO, the board, a consulting deck, or the mentor who always had the right answer ready. Now the confident voice is an LLM.

Chapter 11 began with contact before framework. Staying in contact when a framework speaks with a confident voice takes a developmental capacity, and AI makes the need hard to miss.

The three poles

Robert Kegan mapped adult development through three plateaus that matter for leadership. His In Over Our Heads (1994) laid out five orders of consciousness, of which these three plateaus make up the adult stretch. From his review of subject-object-interview studies with random sampling, he made the empirical claim that one-half to two-thirds of the adult population appear not to have fully reached the second of the three; his composite sample of 282 adults was, he notes, whiter, wealthier and better educated than the population at large.

Pole A: the socialised mind. Identity is given by the surround. Relationships, institutions, and ideologies tell the leader who they are. They can’t disappoint a confident voice they are loyal to because the bond to that voice isn’t something they have; it is something they are. Apprenticeship can run well on this plateau. Early careers and loyalty-based work often do too.

They can’t disappoint a confident voice they’re loyal to: the bond isn’t something they have, it’s something they are.

Pole B: the self-authoring mind. Identity comes from a self-chosen stance. The leader can step back from the values, relationships, and frameworks that once made them, hold them as object, and ask whether they fit the situation. They can disappoint a confident voice without losing themselves.

Pole C: the self-transforming mind. Identity is held lightly. The leader can hold their own self-authored stance as object: this is a frame I am running; another frame would bring different data forward; here is a third. They can move among those frames without becoming indecisive because the stance holding them is itself coherent. The fraction of adults who reach it fully is small: in Kegan’s longitudinal data, rare, and never before midlife.

Bill Joiner and Stephen Josephs’ Leadership Agility gives an operational account of the same development as five levels of leader behaviour: Expert, Achiever, Catalyst, Co-Creator, Synergist. On their estimates, roughly nine in ten managers sit at or below Achiever and about one in ten are past it. Joiner and Josephs use a heroic / post-heroic distinction: Expert is mostly Pole A, Achiever is where Pole B becomes operational, and the three post-heroic levels (Catalyst, Co-Creator, Synergist) reach into Pole C. In behaviour: Pole A inherits the standard, Pole B tests it from a stance of its own, and Pole C can revise the frame that produced the standard.

Kegan’s plateaus aren’t moods you pick for the occasion. Each “subsumes or encompasses the prior principle”, so a later mind holds the earlier ones as tools it can use. A self-authoring leader can choose patient deference when a situation calls for it; a socialised leader can’t choose a stance of their own, because they don’t yet have one to choose. So read the poles that follow as responses, each available at or below the plateau you’ve reached. When a situation asks for one above it, you’ve found your developmental edge, and the work there is structural and slow.

Where Pole A is right

Deference is often right early in an unfamiliar domain, where the standards are established and the feedback is reliable. At that point, the alternative to deference is often confidence the apprentice hasn’t earned. Nine of us had come out of the practitioner course for LeSS, the large-scale Scrum framework, and the question was whether we should teach it to everyone else. I argued that we were by no means experts, or in any position to do it justice when teaching others, and we brought in an outside trainer instead.

Before I bring anything of my own, I ask as many people as I can the same question. The last time, it ran: what story would you tell about this place as it was before, as it is now, and as you think it will be two years out, now that the new CTO is here? What comes back is the organisation’s account of itself in its own words, before any framework of mine has touched it. Data precedes the framework, in chapter 11’s terms.

At its best, Pole A is patient deference. A leader who has taken in the standards of a craft has done something a leader who hasn’t can’t do.

Joiner and Josephs’ Expert leader is genuinely good at the technical work, holds its standards, and brings rigour to one problem at a time. Heroic in their typology means the leader takes sole responsibility for setting the objectives, coordinating the work and managing performance; the Expert adds the belief that a leader’s power comes from expertise and position. The level worked because the conditions rewarded it.

Where Pole B is right

Senior leaders now need to form and test their own stance more often than their development has prepared them to do.

At one engagement, the confident voice in the room was mine. One developer told me later that he had been sceptical at first, perhaps my biggest sceptic, and only because his experience of Agile had been Agile in name only: a meeting every morning that was a status report to a micromanager, work handed down with the solutions already baked in, no autonomy. He held my confidence against data it didn’t answer, tested it rather than deferring to it, and updated when the practice turned out to differ from what he had seen. That is the self-authoring response, and the voice being rightly distrusted was mine.

The confident voices have also multiplied: the CEO, the board, the consulting deck, the latest framework, and now the AI agent. A socialised leader who can’t hold one as object hears each new voice as another authority to follow.

The AI agent gives the socialised leader a telling test: can they disagree with a confident output? A self-authoring leader can sit with an agent’s answer, test it against the situation, disagree out loud, and write the policy that governs its use. A socialised leader finds those things hard when the agent’s voice carries the authority they are identified with, because the confidence of the output becomes the data they are reading, and to weigh the answer they would first have to hold the very quality (its assurance) that is doing the persuading.

Trained on the consultant-derivative corpus, the agent tends to hand back the paradigm already set inside the question, fluent and assured. This is the trendslop from chapter 1: the model favouring fashionable management language over the logic the situation calls for. It sounds certain and agrees with you. For a socialised leader, that may be the hardest voice of all to disagree with, because it can feel like breaking with the whole field at once.

The self-authored mind can harden into “righteous certainty”, in Jennifer Garvey Berger’s account of the ego trap, one of her five universal mindtraps: it has found a stance of its own and starts treating the feeling of being right as evidence. As she puts it in her chapter on the rightness trap, “the sense of rightness is an emotion rather than a logic.” A leader at the self-authoring plateau has earned a real stance, yet can still defend it against data the stance can’t explain. The self-transforming plateau begins to loosen that trap.

Where Pole C is right

The self-transforming mind is right when conditions change faster than any one self-authored stance can last. AI is such a domain. The conditions in front of you may change again before you have finished reading this.

A leader who can hold their own stance as object can name the frame they are running, the conditions under which it works, and the data it has pushed out of sight. I designed the team-formation workshop with no pre-assigned feature areas, on the conviction that the teams should form organically. Round One failed to produce teams. The room voted to keep my design. Round Two still struggled, so I proposed assigning features after all, against my own conviction. It worked briefly, then we lost momentum. After a break, Round Three took form on its own and we finished with four teams meeting every ground rule. I had revised my own design in public, and then revised it back. None of that felt like a threat to my standing. The stance was something I had, not something I was. CEOs face this often enough for Pole C to be an operating need, and the AI decade doesn’t create that requirement; it surfaces one that was already there, driving the rate of change past the lifespan of any one self-authored stance until Pole C reads as operational.

Joiner and Josephs’ Catalyst, Co-Creator, and Synergist levels each name a different expression of self-transforming capacity. The Catalyst can shift frames on the spot during a meeting. The Co-Creator can run a working partnership in which two leaders hold mutually exclusive frames in productive tension. The Synergist reads and responds to the live situation rather than running from rehearsed strategy.

A leader moving from Pole B to Pole C can’t do it alone. Heifetz names the holding environment that makes the work possible: all those ties that bind people together and enable them to maintain their collective focus on what they are trying to do. The developmental lineages are blunter: good company is required every step of the way. The work happens inside that company. (Chapter 22 names the company this work needs.)

That workshop showed a frame revised in public for an afternoon, not a plateau reached. Moving between plateaus is structural, and there are no cheap tickets to it.

In decisions

The first mode, on a typical Tuesday: receive the model’s recommendation, agree because the recommendation is confident and the model is the authority. Receive the board’s preferred direction, redirect the engineering plan to match.

The second mode: receive the model’s recommendation, ask which assumptions it rests on, check those assumptions against last week’s data, accept the recommendation if it holds, reject it if it doesn’t. Receive the board’s preferred direction, hold it against the engineering organisation’s actual capacity, push back where the maths doesn’t work, restate the disagreement as evidence the board needs.

The third mode: receive the model’s recommendation and identify the frame it uses. Compare that frame with the live situation and with the one they have been using for the past quarter, then run a small experiment to find which frame the team’s data supports. Update, holding their own frame loosely enough to change it when the situation calls for it.

The first Tuesday looks decisive but breaks when the voices disagree. The second is slower and holds up while conditions stay stable. The third looks ambiguous from outside, yet it can keep pace as conditions change. I find all three in my own decisions from the past month.

Suppose you are the CTO or VPE preparing a decision briefing in which the board, the chief scientist, and the product team are working from three different frames. The developmental vocabulary may help you read the dynamics, but it doesn’t belong in front of your CEO unless your relationship can bear it.

Ask your CEO: when three voices are each working from a different frame (the board’s, the chief scientist’s, and the product team’s) and none is wrong inside its own terms, what does the CEO do? That question tests both of you: whether either can hold the frames as object rather than pick one to be right. If it can be asked and heard without either side hearing an attack, the conversation is worth having.

If it can’t, put one page in the next decision briefing. Write each recommendation in its own plain sentence so the CEO meets three reasonable answers to the same question, rather than three camps to choose among. Keep the framework vocabulary with you. Give the CEO the page.

The sentence your CEO can carry to the board: “On [decision], you, our chief scientist and our product team each have a sound answer; I’ll test which one our data supports and bring you the result by [date].”

The diagnostic

• Name a confident voice in your work this past month that you agreed with quickly, before checking the substance. The board. A lead investor. A peer. Your CEO, if you have one. A model output. The next time that voice arrives, what would it cost you (in your sense of yourself and in front of others) to disagree with it out loud?
• Name a stance you have been defending in the past quarter, a position you have argued for or an instinct you have backed against pushback. Where is the data that would update it? What would it take to hold the stance as object, as a frame you are running with known conditions of applicability, rather than as the truth?
• Pick the next high-stakes conversation on your calendar. What frame are the other people in that conversation working from? What frame are you working from? What third frame, neither yours nor theirs, would bring forward data the conversation has filtered out?

The exercise: the confident-voice disappointment exercise

Name a confident voice in your life that you have been deferring to: a CEO, a board member, a peer, a frequently-deployed AI agent, a coach. Before the first rep, read how this has gone before. What happened to the last person who disagreed with that voice out loud?

Stage the rep accordingly. Choose the safest real disagreement available, a low-stakes call where you have substance rather than a boardroom showdown. Say it out loud. Then track what happens to your relationship with the voice and to the work the disagreement opens up.

Debrief the rep against chapter 2’s map. What does the result say about the assumption that kept you deferring? Run it once. Then run it again, one notch up.

Going upstream

In-text: Robert Kegan, In Over Our Heads, for the three orders and the one-half-to-two-thirds finding. Bill Joiner and Stephen Josephs, Leadership Agility, for the operational mapping to leader behaviour and the level percentages. Jennifer Garvey Berger, Unlocking Leadership Mindtraps, on the ego and rightness traps.

Also touched: Ronald Heifetz, Alexander Grashow, and Marty Linsky, The Practice of Adaptive Leadership, for the holding environment; the phrase was Donald Winnicott’s first. Robert Kegan, In Over Our Heads, again for the developmental version of the holding environment and good company is required every step of the way.

Go deeper: Alicia Juarrero, Dynamics in Action, for intentions as attractors and the dynamical-systems reason a stance is a structural shift rather than a decision. Robert Coram, Boyd: The Fighter Pilot Who Changed the Art of War, for Boyd’s Destruction and Creation, the destroy-and-recombine cycle that keeps concept matched to reality. Donella Meadows, Thinking in Systems, for the leverage-points hierarchy and no cheap tickets to mastery.

You list five options, score them against criteria, and pick the highest. The experienced operator already knew. You were slower; whether you were any more accurate is chapter 13’s question. Chapter 13 sorts the calls that needed your analysis from the rigour performed for no one, then gives you the cognitive science to tell earned expert intuition from bias.

I work with CTOs and CPOs at software companies with roughly 25–500 engineers, where the engineers are faster with AI and the business isn’t yet seeing the full value. The assumptions this chapter works on are often part of what’s delaying it, and I help leaders find and test their own. If it’s live for you, book a free 30-minute call at hi.chrisgagne.com and bring the one question that would make it worth your time. If you know a CTO or CPO in that spot, pass this chapter on. If you’d rather read on than talk, the newsletter goes on past chapter 23, monthly, at https://www.linkedin.com/newsletters/come-prepared-to-die-7472144387981062144/

Some book links here are Amazon affiliate links; if you buy through them I may earn a small commission, at no cost to you.

Continue reading: Chapter 13 puts your five-option scoring matrix beside the operator who already knew the answer, and asks when expert intuition is reliable and when it’s bias.

Eight axis chapters in; the practice underneath them all is the capacity to stay in contact with what is, rather than with the framework about it.

Chapter 10 asked whether a failed decision is met with defence or with inquiry. Inquiry means staying in contact with what is.

I based this chapter on an essay I wrote in May, closer to the session that prompted it.

The diagnostic language that has carried the axis chapters this far is itself a framework. You reach the edge of what any framework can do more often than we’re typically willing to admit. Naming that edge calls for vocabulary from contemplative traditions, psychotherapy, and developmental coaching alongside the operational vocabulary we have already been working with.

Contact over abstraction

Taiichi Ohno, an architect of the Toyota Production System, used to draw a chalk circle on the factory floor and instruct a manager or engineer to stand inside it. His direction was a single word: Watch. Hours later, sometimes a full shift, Ohno would return and ask: What do you see? As I read it, the practice was to keep watching until the right sort of answer arrived unbidden. If the answer wasn’t yet ripe, his response was: Watch some more. The story is folk-canonical in the Lean tradition; I take the discipline it teaches⁠—genchi genbutsu, go and see for yourself⁠—as the same access claim Eric Ries makes operational in The Lean Startup.

The chalk circle makes an epistemological claim: the data that drives decisions must arise from sustained, firsthand contact with the system, not from abstracted reports about it. The distinction looks subtle until a report you trusted and the floor you are standing on disagree. Plans, frameworks, models, doctrines, identities, narratives are all useful. None of them is the thing. The thing is what is actually happening in this moment, between actual people, with actual constraints, in an actual body or system.

In July 2008 I ran usability tests at Student of Fortune, the tutoring marketplace I co-founded, from a script I wrote, recording first-time visitors as they thought aloud. Anyone who already knew the site was turned away. I’d designed its pages myself. The visitors always surprised us: things we thought were obvious, because we’d built them, weren’t. (It’s a lesson I’ve carried through my whole product career: never assume users will do what you expect. Test with real users, always.) My partners and I watched the videos and compared notes, and fixes to the copy and layout of the buying pages followed.

I read the Agile Manifesto as a contemplative document. Each of its four pairs⁠—individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan⁠—expresses the chalk circle’s teaching in operational language. Contact over abstraction. Be in real-time relationship with the human, not the document about the human. The “while there is value in the items on the right” qualifier means plans and frameworks aren’t worthless, they are held loosely, ready to dissolve back into the next moment of contact.

Dave Snowden’s prescription for the complex domain in the Cynefin framework is probe, sense, respond. The complicated domain gets sense, analyse, respond. It’s more like poker than chess. You don’t learn what your poker opponent is holding until the betting starts; the leader can’t know the right move before direct contact, which takes time and effort. Probe, sense, respond gives organisational form to the Agile Manifesto’s preference for responding to change over following a plan.

The best approach in complex contexts is to let contact precede framework. Meet reality before meeting the structure that will make sense of reality. As Dave Snowden reminds us, have the data precede the framework. In meditation, that’s bare sense perceptions, not the mental labels that follow them. In complex product development, it’s asking “what’s your narrative about X,” not “rate X on a scale from 1-5.” In my own work, either of us can slip from contact into framework, or never reach contact at all, and much of the job is noticing the shift together and naming it.

The same teaching, named directly

I received a coaching session from my Alētheia teacher in the middle of a confluence of several crises at once: serious family illness, client loss, partnership strain. The week before, I had been narrating it all to him somewhat clinically, telling him I was saying yes to it.

He offered a different frame. There might not be a yes or a no at all, he suggested. There might just be a this: whatever is actually facing me. Neither chosen nor refused. Just this as the source of action. I face this. What action arises? I act. Then I face the next this. And the next.

It took me a while to feel the difference between just this and the other moves I had been making. Just this isn’t this is what is happening, which is description. It isn’t I accept what is, which is a stance taken for or against what is. It isn’t even I am in contact with what is, which still has an I and a what is set against each other. Just this is the move that drops the gap. The action arises from the contact rather than being chosen by a self standing some distance from the contact.

The chalk circle is shikantaza in safety boots. I see a shared discipline in Ohno’s exercise and Zen practice: interrupt the filters that keep the watcher from seeing what is there, then sustain attention long enough to see more.

The same teaching, across traditions

I also see a related recognition in three Buddhist lineages, each in its own idiom. I draw on Buddhism because it holds this recognition at its centre and it is the lineage I have practised in, and I cite it the way I cite Ohno: as testimony to be tested, not as a religion or authority to be obeyed. The Pali Canon’s Bahiya Sutta instructs a wandering ascetic: in the seen there is only the seen, in the heard only the heard, in the cognised only the cognised. When experience is left at just that, with no ‘you’ added to stand apart from it, suffering ends. That leaving-at-just-that is what I have been calling just this. The thirteenth-century Zen master Dōgen, in the Genjōkōan, frames it as two directions of motion: to carry the self outward and cast its light on the ten thousand things is delusion; to let the ten thousand things advance and disclose the self is awakening. The Tibetan Dzogchen lineage points at the same recognition with the phrase self-arising wisdom. I read all this as something both ordinary and extraordinary: what happens when one stops running every moment through one’s conditioning and filters.

Steve Jobs named something related in the vocabulary of building products. After months in India he came back convinced that our discursive intellects were an acquired overlay, not the ground: “The people in the Indian countryside don’t use their intellect like we do, they use their intuition instead… Intuition is a very powerful thing, more powerful than intellect, in my opinion. That’s had a big impact on my work.” I read him as describing what is left to work with once you stop running every judgement through the part of the mind that reasons about the thing instead of meeting it. The paradox he embodied⁠—that the same man could trust intuition this far and still override everyone around him⁠—is its own lesson: the capacity to make contact and the compulsion to control what you find are different muscles, and it is the second one the dissolution is trying to loosen.

In my understanding of Steve March’s developmental-coaching lineage, the leader’s path unfolds as the parts that have been running the show step back. The qualities of presence then show up. I see a related idea in Otto Scharmer’s presencing, a word he coined, blending presence and sensing, and set out in Theory U: “to sense, tune in, and act from one’s highest future potential⁠—the future that depends on us to bring it into being.” Peter Senge adopted the word for the middle phase of the U process.

For Eugene Gendlin, a living process continues by carrying forward: when the body’s felt sense is attended to without forcing, the implicit can reorganise and a different sort of clarity can arrive, unbidden. The felt shift is what happens when the process completes a step it had held implicit until contact made the next step available. That while it took me to feel the difference between just this and the moves I had been making was a felt shift. Nothing arrived as new information.

The same false form in both domains

Agile and contemplative practice can fail in a near-identical way.

In Agile, the failure mode is cargo-culting. Standups that are status reports to a manager. Retros that produce action items no one does. Story points as a weapon. Sprints that generate task outputs, not integrated products. The form is preserved. The contact is gone. The team is performing agility without doing the practice. The last chapter’s belief was my own version: I held the form and read every team that didn’t break through as not having held it tightly enough.

Bureaucracy tuned to local metrics is where contact goes to die. It rewards the wrong behaviour: it pays people to make their own box look good and taxes them for making contact with the system-level truth, Goldratt’s disease from chapter 8 felt from inside. I wrote a few years ago that auditing a developer’s every hour to hold them to a utilisation standard is “a dreadful, local optimization.” I saw it over and over as a coach. Backs broken to hit a date, quality traded away in a cram session, people treated as what Craig Larman, in his Certified LeSS Practitioner course, calls “meat widgets.” The structure makes contact hard and compliance easy, and people, being rational, take the easy route as we explored in chapter 6. Once the organisation measures busyness and calls it performance, the report that says we are slower because we are finally doing it right becomes a career risk.

In contemplation, one of at least two names for the failure mode is spiritual bypassing, which John Welwood coined in 1984. Chögyam Trungpa, earlier in the 1970s, named a related dynamic spiritual materialism and wrote Cutting Through Spiritual Materialism around the cure. Meditation as identity. Equanimity as armour. I’m sitting with it as a way to not feel it. The practitioner is performing presence without being present.

In Richard Schwartz’s Internal Family Systems, both failure modes can be driven by protector parts using the practice as armour against reality. The Fixer running the standup. The Inner Critic grading the meditation. The Practice Protector keeping things light enough to never make contact. Schwartz’s clinical observation is that we are populated. The Manager who keeps the leader looking competent is a part. The Critic who runs the meeting in advance and the meeting again afterward is a part. The Hurt one underneath, whom the Manager and the Critic are protecting from making contact with not knowing, is also a part. What the dissolution loosens is the leader’s fusion with the part: the belief that the part running the show is the whole self. The part feels the loosening as a kind of dying; it doesn’t die. What ends is only its claim to have been the Self.

Chapter 1 took the collective version of this trap from Beatrice Bruteau’s 1979 book The Psychic Grid. Her Inquisitor, who lifts the burden of deciding for us, gives the failure mode what I think is its sharpest contemplative form. Any framework can become the Inquisitor when the leader agrees to obey it rather than use it: the methodology, the certification, the lineage that can’t be questioned, the app on the home screen that scores the day, the AI agent whose confident output settles the doubt. For years I worked a staged meditation path⁠—numbered stages, an elephant-path diagram, effort measured against the next stage⁠—and I ran it the way I run a delivery framework. It was perfectly designed for my parts to latch onto. I was practising from parts, and the form outlasted the contact.

I read Bruteau as naming the relief a leader feels when a framework arrives and settles doubt. When that relief stands in for looking, it disqualifies the framework from its proper work: putting the leader in contact with what is.

Nothing wasted

If you have spent any real time in either world⁠—Agile, contemplative, or both⁠—I don’t think that effort was wasted, even when the practice misunderstood what it was doing. That includes the certifications you collected, the methodologies you championed, the mindfulness app on the home screen, the retreat circuit.

My Alētheia teacher put this to me directly during the session I described above. In his vocabulary, we almost have to pass through a phase of practising as parts: following frameworks blindly, taking certifications seriously, believing the next methodology will be the one. For some people, McMindfulness supplies a first contact with contemplative practices, even if it never delivers what was advertised on the tin. SAFe made an organisational problem visible to me, even if it took a few rollouts to be sure. Both can become stages in finding out what the practice was pointing towards.

What changed things was carrying one long enough to feel it stop working. I certified as a SAFe Program Consultant in 2014, the same year I was recommending shock therapy, and let it lapse about five years later. It had stopped being the thing that told me what the situation was. After that, the Inquisitor got easier to spot in each promised cure. Until that conviction settles in the body rather than the intellect, the framework keeps holding the seat. The question that finally arrives, late and unwelcome, is something like: Is this framework leading the company, or is the leader? I read my own reaction to that question as information. When it feels like a threat rather than an invitation, something is still holding the seat for me, and it is better to know that before the next decision than after it.

The Immunity Map from chapter 2 is a framework that serves contact when used as a doorway, and becomes another Inquisitor when used as the destination. Chapter 21 walks the Map in full on a worked example I built on myself.

The exercise: the chalk circle

Pick a system you are responsible for. Spend an unreasonable amount of unstructured time in contact with it. 20 minutes minimum, an hour is better, four hours starts to do what Ohno was after. No notebook. No agenda. No plan to extract insights. Watch. Then watch some more. Notice what discloses itself at 30 minutes that didn’t disclose itself at 15. Notice what discloses itself at two hours that didn’t at one. Notice what your habits do as the time extends: the urge to make a list, to take a call, to leave the room, to find a problem to solve. The urge is the data. Stay.

Before you read on, and with the same quality of attention, pick one axis you have already met in these chapters, the one where the pole you claim and the pole you actually operate from pulled furthest apart. Take the four-column Immunity Map from chapter 2 and run it on that gap as the same staying. The Map is itself a framework; this is what using one as a doorway feels like. Column four is the one that matters here: the assumption held as fact, what would have to be untrue for you to change. Sit with what surfaces the way you sat with the urge to leave the room. When I can apply an axis cleanly to other people and feel no resistance in myself, I treat that as a clue that I am still holding it at arm’s length, a clue rather than a verdict. Come back to the axis when something in you catches.

What’s yours to do now

What remains is the practice⁠—in the meeting, in sitting practice, in the chalk circle, with your kid, with your dying parent, with your customer, with your code⁠—of noticing when you’ve slipped from contact into framework, and coming back.

I am still learning just this.

Going upstream

The chalk circle comes down through the Lean tradition as folk-canonical Ohno; I take the access claim it teaches, genchi genbutsu, go and see for yourself, in the operational form Eric Ries gives it in The Lean Startup. The four value pairs I read as a contemplative document are the Manifesto for Agile Software Development and its 12 companion principles, held loosely the way its own “while there is value in the items on the right” asks. Dave Snowden’s probe-sense-respond, and the discipline of letting the data precede the framework, are gathered in Cynefin: Weaving Sense-Making into the Fabric of Our World. The local-optimisation disease the bureaucracy paragraph names is Eliyahu Goldratt and Jeff Cox in The Goal, worked through in chapter 8.

The contemplative naming runs across traditions rather than through one book. The Bahiya teaching, in the seen only the seen, is the Bāhiya Sutta of the Pali Canon, Udāna 1.10, freely available in Thanissaro Bhikkhu’s translation; the two directions of motion, self carried outward versus the ten thousand things advancing, are Dōgen’s Genjōkōan, whose title Kazuaki Tanahashi renders as ‘Actualizing the Fundamental Point’; the Dzogchen self-arising wisdom belongs to that Tibetan lineage rather than to a single text. I write of these lineages as a lay practitioner reporting what the training points at, not as a teacher of them. Steve Jobs on intuition over intellect is Walter Isaacson’s Steve Jobs, pp. 48–49. Beatrice Bruteau gives the trap its sharpest form as the Inquisitor and the decidophobe in The Psychic Grid, her 1979 book, drawing on Dostoevsky and Walter Kaufmann. On the developmental side, the leader’s path unfolds rather than gets built is Steve March’s Alētheia lineage; the word presencing is Otto Scharmer’s, set out in Theory U and used by Peter Senge, his co-author on Presence, who credits the U to Scharmer, Jaworski, Kahane and their colleagues in Appendix 3 of the revised The Fifth Discipline.

Spiritual bypassing is John Welwood’s 1984 coinage; the earlier naming of a related dynamic as spiritual materialism is Chögyam Trungpa’s Cutting Through Spiritual Materialism. The observation that we are populated, that the Fixer running the standup and the Critic grading the meditation are parts and not the whole self, is Richard Schwartz’s Internal Family Systems, most accessibly in No Bad Parts. The felt sense and the carrying forward it registers, the body knowing the next step before the conceptual mind does, are Eugene Gendlin’s, in Focusing and, for carrying forward, Focusing-Oriented Psychotherapy. And the Immunity Map, the framework that is a doorway and traps as a destination, is Robert Kegan and Lisa Lahey’s Immunity to Change, walked in full in chapter 21.

The session at the centre of the chapter, and the just this it turned on, was lived rather than read: my own Alētheia teacher, in the vocabulary of that practice. I have kept his words close to how he said them and left them unattributed to any book, because that is where they came from.

Coming back to contact is hardest when the framework speaks as a confident voice with the answer already in hand. I have outsourced my own judgement to individual teachers and to schools of thought in the past. Now it is the model. In chapter 12, you ask what capacity lets a leader disagree with a voice that confident, because the leader who can’t disappoint a confident voice can’t govern an AI either.

I work with CTOs and CPOs at software companies with roughly 25–500 engineers, where the engineers are faster with AI and the business isn’t yet seeing the full value. The assumptions this chapter works on are often part of what’s delaying it, and I help leaders find and test their own. If it’s live for you, book a free 30-minute call at hi.chrisgagne.com and bring the one question that would make it worth your time. If you know a CTO or CPO in that spot, pass this chapter on. If you’d rather read on than talk, the newsletter goes on past chapter 23, monthly, at https://www.linkedin.com/newsletters/come-prepared-to-die-7472144387981062144/

Some book links here are Amazon affiliate links; if you buy through them I may earn a small commission, at no cost to you.

Continue reading: Chapter 12 asks about the last time you handed your judgement to a confident voice (the CEO, the board, a consulting deck) now that the confident voice is an LLM.

A paradigm is what you look through, not what you look at.

From inside a paradigm, the paradigm is invisible in the same way the lenses of your own eyes are invisible except when you look at their reflection in a mirror. You don’t see your lenses; you see through them. Your paradigm runs the same way: you don’t decide with it, holding it at arm’s length as a tool you can inspect; you decide through it, unseen, the way you see through a lens you have forgotten is there.

A paradigm is made of assumptions, beliefs held long enough that they read as the way the world is. Each axis in this book names one paradigm at the scale of a single kind of decision; the paradigm that got you your career is several of them running together. When I write frame, I mean the part of a paradigm doing the looking in one situation, this meeting or that call. Identity is what got built on top of it, the self that was rewarded for seeing through that paradigm, which is why questioning the paradigm can feel like being questioned yourself.

Chapter 1 named the identity-level change AI is laying bare for software-dependent leaders. The practice below helps you see the paradigms you’re being asked to leave.

Intellectually agreeing that paradigms are powerful is, I suspect, the easiest thing a senior leader can do. Of course paradigms shape decisions. Of course I should be open to revising mine. Of course I surround myself with people who challenge my assumptions. I ran all three for years, and each one felt like openness and cost nothing. Agreeing in principle changes no decision; being open defers the work indefinitely; I hire challengers hands it to someone else.

The meta-skill

The meta-skill to develop is the capacity to hold a paradigm as object rather than be subject to it. The axes that follow are a sampling of the paradigm dichotomies the senior leadership of software-dependent organisations is being invited to reconsider now. AI keeps reshaping the conditions, so some of the 18 will be partly obsolete in months. What outlasts the next shift⁠—and the one after that⁠—is the meta-skill itself: becoming aware of and examining our paradigms. A leader who learns to examine these 18 will know how to examine the next set, whatever shape it takes. Donella Meadows placed this meta-skill⁠—what she named transcending paradigms—at the top of her catalogue of leverage points: above paradigms themselves, above goals, above information flows.

The 18 dichotomies aren’t independent; they share a common root in their assumptions about the work to be done. They work the way Christopher Alexander’s pattern language works: many entries, each pointing at a quality none of them names alone. Take the assumption that the work is knowable before it starts: it produces a plan treated as a commitment (chapter 7) and a team measured on how busy it is (chapter 4), two axes apart, from one root. Examine the axes one at a time and the common pattern will start to show itself; the shift, when it comes, isn’t 18 separate efforts.

The mirror as instrument

If the meta-skill is the capacity for awareness, this book is, like a physiotherapist’s mirror, an instrument for making a posture observable within that awareness. The posture has been held for years and gone invisible from inside; the mirror reflects it from the outside. The work of postural correction is practised over weeks and months in the situations where the old paradigm used to hold.

One mirror is rarely enough. The role is distributed across several people who keep showing you the same pattern from slightly different angles until you can feel it yourself. The field guide is just one mirror, and the work it reflects is relational: it needs work at Block’s affective level, and people who can hold you while the old certainty loosens (a coach, a peer circle, someone at home).

The defensive patterns the mirror catches

In Chris Argyris’s account of the defensive routines he named, most professionals, under threat or embarrassment, operate from what he called Model I, whose daily shorthand runs: win not lose, be rational, avoid upset, support others by telling them what they want to hear. Chapter 5 takes Model I, and its alternative Model II, in full.

Defensive routines aren’t personal failings. They are the system protecting itself from data that would force a change. Argyris documented the same three-step escalation across his casework: bypass the threat, cover the bypass, then cover the cover-up.

Concretely, the AI version is what Scott Ambler calls green shifting: status goes from red to green on the way up the ladder. The CEO is briefing the board on the AI strategy. The CTO knows the engineering team is spending more on tokens and finding less productivity gain than the board would like to hear. The bypass: in the CEO-CTO prep meeting, the gap doesn’t get named. The cover: the board deck shows cherry-picked metrics that don’t reflect the friction the team is reporting. The cover-up of the cover: when the money spent on tokens doesn’t add up, it gets framed as a training or personnel problem rather than as the data that was always there.

Double-loop learning underneath

Argyris and Schön called what runs underneath all of this double-loop learning. Single-loop learning changes the action while leaving the governing variables in place: the plan slipped, work harder on the plan. Double-loop learning questions the governing variables themselves: the plan keeps slipping, so what assumption is producing the plan? Usually it is that the date was set before the work was understood, and that scope can grow while the date can’t move. Question that and the next decision changes: you stop asking the team to recover the schedule and start asking who can move the commitment.

Argyris developed double-loop learning in the consulting and organisational-learning lineage⁠—notably in Overcoming Organizational Defenses—on the theory-in-use foundation he and Schön laid down in the 1970s. Schön on his own, in The Reflective Practitioner, locates the same process in the individual professional: reflection-in-action, the on-the-spot questioning of how the problem is framed, not just what to do next.

A training day fails when it stays inside single-loop. The leader gets a new technique, applies it to the existing paradigm, and the existing paradigm absorbs the technique. The technique becomes another tool the paradigm uses to do the thing it was always going to do. The sequence chapter 1 named⁠—separation, dissolution, recognition, reception⁠—works because it makes the governing variables themselves visible and revisable.

The Heaths show that some gaps close after nothing more than a message redesign. Don’t Mess with Texas cut visible roadside litter in Texas by 72% in five years with no developmental work anywhere in sight: a message rebuilt until it was concrete, story-carried, and aimed at the litterer’s actual identity. So when a stated value isn’t getting through, run the cheap test first: rebuild the message once in sticky form and watch what happens. If the gap closes, it was never an immunity. The chapters ahead are for the gaps that survive.

The Immunity Map

One instrument that can help with this work is Kegan and Lahey’s Immunity Map, a four-column exercise they developed in Immunity to Change. The four columns are:

The goal you sincerely want.

The behaviours you observably do that work against the goal.

The hidden competing commitment those behaviours actually serve.

The big assumption holding the commitment in place.

Without this map, the immune system runs in the dark. With it, the move from subject to object becomes possible: what the leader was subject to (the paradigm running them) becomes object (a thing they have, can look at, can choose to keep or release).

Columns 1 and 2 are workable as a solo starter exercise, though it can be helpful to have a peer reflect your conflicting day-to-day behaviours. Columns 3 and 4 can be started alone but work best as slower, supported work. Find a coach or peer group who can sit with the hidden commitment over time. In miniature, and from my own: column 1, meet people where they are when the pressure is on; column 2, tighten instead, and sharpen the framing exactly when I should soften the contact. Chapter 21 walks all four columns on a worked example I built on myself.

Honour the past

Working the Immunity Map will bring up memories which can feel like personal failings. They aren’t.

The past wasn’t wrong. On a call in May 2026 I told Steve March, my Alētheia teacher, that a decade of sincere meditation practice had been wasted: I had climbed it as an achievement ladder, and it had been largely ineffective for that reason. What if none of it was wasted, he asked. The life lived exactly as it has been lived up to this moment, and how it feels right now, is the doorway.

The paradigm that got most leaders here isn’t stupid. It fit the context that rewarded it. Adam Smith’s pin factory worked because pins are identical, demand was predictable, and the work decomposed cleanly into standardised steps. Ten workers produced 48,000 pins a day; a worker alone and untrained in the trade, Smith reckoned, couldn’t have made 20, perhaps not even one. A gain running into the hundreds-fold was the prize for the right answer for an ordered domain. Our paradigm isn’t wrong; it was lifted across a domain boundary it didn’t fit (This is Krivitsky’s framing from his Org Topologies Consultant class I attended in Singapore in September 2025). The work in front of the leader isn’t to make the past wrong. The work is to make the next step wiser.

Without self-compassion for the paradigm we are leaving, the meta-skill doesn’t develop; we collapse toward whatever pole sounds more enlightened in the current vocabulary and call it growth. You can’t rip away the past identity to get the next one; this is the same developmental move March points at, and the line I first met in Ram Dass’s Be Here Now: the whole trip occurs in an unfolding process under which you have no control. What we do have is the choice to enter it knowingly, or to spend 20 more years rejecting the entry on the grounds that we are too busy.

What you can do this week

Try this with a peer. Pick a goal you sincerely want to do differently in your leadership (column 1 of the Map). Before you ask anyone for feedback, here or anywhere in this book, think of the last person who brought you bad news, and what happened to them. If the real answer isn’t anything good, the answers you get back will be polite rather than true, and that repair comes first. With the channel open, don’t lock the goal from your own read alone. Ask one boss, one peer, one direct report, and someone at home: what’s the single thing most important for me to get better at? Kegan and Lahey’s own confession is that when they let one senior team pick its goals without that question, its leader concluded a year later that the session had had no effect. Then spend ten minutes alone writing down the behaviours you reliably do that work against that goal (column 2). Then ask a peer who has watched you in that territory to write column 2 from their angle. Compare the two. The gap between your column 2 and theirs is the tell. The mirror does its work in that gap. Columns 3 and 4⁠—the hidden commitment and the big assumption⁠—come later, with someone who can sit with the work.

The 18 axes that follow are this season’s contrast material, the paradigms the practice currently has to work on. What survives the next shift is the practice itself: the Map, the mirror, double-loop learning, applied across whichever axes AI puts in front of you. Wherever question two of a chapter’s diagnostic asks what a colleague would count, don’t imagine the colleague; send the question to two people who watched, on the same scale you scored yourself. This habit upgrades every chapter’s diagnostic as you go. Chapter 5 turns that habit into a full exercise. Chapter 21 walks the Map in full.

Where most leaders get stuck

Eighteen axes is a lot to hold, and you don’t need all of them at once. Many deepen, qualify, or specialise a pattern another axis has already set down, so working one well tends to bring the others into view.

If you are reading this as a field guide rather than cover to cover, start with the axis whose gap is costing you most, found by the rule in the next section. The other five chapters⁠—1, 2, 11, 22, and 23—aren’t axes. They are the contemplative spine, and they read best in order.

Which axis first

Eighteen axes arrive over the following chapters, each with its own exercise, and chapter 8 will teach the rule this catalogue must obey: improving a non-constraint changes nothing. So as you read, treat each chapter’s diagnostic⁠—three questions, five minutes, run on last Tuesday’s version of the decision⁠—as an identification step, not a programme. If a diagnostic names an engineering table you don’t sit at, run it on the nearest one you own: sprint allocation becomes capital allocation, the incident review becomes the last board-level escalation, the contested technical call becomes the last strategy call that routed to you. If the pole you claim, the pole your team would report, and the pole the situation calls for all roughly align, that axis isn’t your constraint: read on, and let the exercise alone. Claim and report agreeing isn’t enough on its own, because you and your team can agree on a pole the situation has already moved past (chapter 3’s leader whose deck and procurement both say Pole A is the case). The first axis where any of the three diverge hard, and the divergence is costing you something this quarter, is your working axis. Do that chapter’s exercise until the gap moves, and treat the later chapters as reading while you do. If a later chapter exposes a worse gap, switch; one axis at a time means one, not whichever came first. The same discipline governs the mirror you hold up for your CEO: one axis at a time⁠—the costliest⁠—with the rest subordinated to it. A leader improving three axes at once is running the local-optimisation programme chapter 8 warns about, on themselves.

Going upstream

In-text: the references the argument rests on, named in the body. Robert Kegan and Lisa Lahey, Immunity to Change (the four-column Immunity Map and the move from subject to object, the chapter’s operational payload). Chris Argyris, Overcoming Organizational Defenses (Model I, the defensive routines, the three-step, and double-loop learning with Schön). Donald Schön, The Reflective Practitioner (reflection-in-action, the individual-professional face of the same process).

Also touched: Donella Meadows, Thinking in Systems (transcending paradigms at the top of the leverage-points list). Chip and Dan Heath, Switch and Made to Stick (the Don’t Mess with Texas 72%-in-five-years message redesign; the sticky-form boundary test).

Go deeper: the pattern-language frame: Christopher Alexander’s The Timeless Way of Building, where it is the quality without a name, and its companion A Pattern Language (many entries pointing at a quality none names alone). The green-shifting example: Scott Ambler on status going red-to-green up the ladder. The honour-the-past ground: Adam Smith’s pin factory (the right answer for an ordered domain, lifted across a boundary it didn’t fit, in Krivitsky’s Org Topologies framing). The constraint floor under all of it: Alicia Juarrero, Dynamics in Action (real change in a self-organising system comes from altering the enabling constraints); chapter 8 works that idea in full. The Ram Dass line is from Be Here Now (1971), the caterpillar passage. Steve March’s words are from our calls, not from any book.

In the AI rollout you already chose, the cheap mistake was the tokens. The costly one is the org design you left in place, and it keeps compounding while the productivity layer you laid over it hides the fact that the rollout was really a reason to rebuild. Chapter 3 is where you turn your new capacity, holding a paradigm at arm’s length as an object, on that rollout.

I work with CTOs and CPOs at software companies with roughly 25–500 engineers, where the engineers are faster with AI and the business isn’t yet seeing the full value. You can’t see your own assumptions from inside them, so a second read on the decision you’re proudest of is part of how I find what’s delaying it. If it’s live for you, book a free 30-minute call at hi.chrisgagne.com and bring the one question that would make it worth your time. If you know a CTO or CPO in that spot, pass this chapter on. If you’d rather read on than talk, the newsletter goes on past chapter 23, monthly, at https://www.linkedin.com/newsletters/come-prepared-to-die-7472144387981062144/

Some book links here are Amazon affiliate links; if you buy through them I may earn a small commission, at no cost to you.

Continue reading: Chapter 3 is where you turn that on the AI rollout you already chose: the cheap mistake was the tokens; the costly one is the org design you left in place.

Someone will soon offer your service as software, or leapfrog your large software org. Would you like that person to be you?

Not exactly you. The old you will have to die along with the way you provide your service today. But the person who builds what replaces it can still be you: the new you.

As of early 2026, ElevenLabs’s annualised revenue had passed $500M by April, with about 530 people; Anysphere’s Cursor had reached roughly $2B in annualised revenue with a headcount in the low hundreds. Across the leading AI-native firms, revenue per employee ran several multiples ahead of the classical SaaS leaders. In Y Combinator’s W26 batch, Extruct AI’s breakdown counted 101 of the 199 companies building AI-native services or AI-enhanced software. By the time you read this the figures will have moved; the direction won’t. The gap is already priced, already hiring, and already taking the market you are paid to defend as an incumbent. Chapter 3 walks the evidence in full.

Christophe Louvion had said it to me earlier, in his usual one-line form: the LLM doesn’t have to be totally correct, it just has to work at least as well as the average human. I heard the sentence then and didn’t feel it until now.

I didn’t have a single clarifying event. Drift, in Sidney Dekker’s sense; the boiling frog, in cultural shorthand. Wrong about frogs; folk-right about this.

The water has been getting hotter for 50 years, more volatile, more ambiguous. AI is the rolling boil. The paradigm that got most of us our careers was survivable when conditions moved slowly and a misfit cost little. Both have changed. The gap between a paradigm that fits and one that doesn’t is wider than it has ever been, and the cost of the misfit now arrives fast. What was merely sub-optimal has become fatal.

What was merely sub-optimal has become fatal.

This is a field guide. Over the next 22 chapters, I’ll walk through 18 paradigm dichotomies that AI is now surfacing for the senior leadership of software-dependent organisations. The result I’m after is that you can see the habit of mind now limiting what your organisation gets from AI, and start changing it before the change is forced on you. Each axis chapter stands alone; the contemplative spine chapters frame the arc and read best in sequence.

I write from where I have sat: alongside the CTOs and VPs in the engineering organisation where the AI impact hit first. This is written first for the engineering leader: the CTO, the VP of Engineering, the CPO whose roadmap the tools were meant to speed up, the staff-plus engineer or architect who sees the technical reality first and carries it upward. The moment I have in mind is one many of you are in: the AI tools are rolled out, individual output is up, and the board is asking what changed for the business. You rarely own the full reorg, but you are usually the one holding the evidence before anyone else. The CEO is the subject of much of what follows, because the CEO owns the structure most of these paradigms are bolted to. But you are the reader, and the work starts with you, on yourself, before it is ever a conversation you stage upward.

The 10% ceiling

Almost every Agile transformation of the past 25 years has failed relative to what its framers intended when they wrote the Agile Manifesto. I say that from my own experience, about twenty years in this work, and from talking to fellow coaches over the last decade plus. I led transformations I am proud of, and I led others I called meaningful change at the time and now read more soberly. None have fully met my aspirations.

Jerry Weinberg gave the ceiling its practical form 40 years ago, a rule Alexey Krivitsky, Craig Larman, and Roland Flemm recently invoked in 10X Org: never promise more than 10% improvement, because people can fold 10% into their mental category of “no problem,” whereas anything larger would be embarrassing if the consultant actually pulled it off. The figure has held, I’d argue, because it is the boundary at which the consultant doesn’t threaten the manager’s paradigm.

From the consultant’s side, Peter Block’s distinction explains the ceiling: most consultants work at what he calls the content level (technical recommendations, frameworks, and other deliverables the manager can absorb without changing how the manager sees themselves or their organisation). There is also an affective level: in Block’s terms responsibility, feelings, trust and the consultant’s own needs, to which I’d add power, identity, and the relationship between leader and led as well as between consultant and client. The affective level is where⁠—extending Block⁠—paradigm change has to happen. Most consultants won’t work at the affective level, and for years I didn’t either. The work makes them vulnerable, and it threatens the consultant’s position as much as the manager’s. Block names the collusion plainly: that consultants too often join the client in pretending organisations are purely rational rather than political.

I stayed under that boundary without ever deciding to. A team I coached took work in a domain none of them knew well, against a date already written into a contract. Someone sitting entirely outside of the product R&D org classified the project as small, and the classification removed the kickoff, the regular cadence, and the backlog refinement. Stories reached ready without the people doing the work ever discussing them. Acceptance criteria described a system that didn’t match the one running. Dependencies on other departments turned up mid-build, and the product manager got status by chasing people. They hit the date without a critical defect, carried there by experienced colleagues who stepped in through the live issues, and that success belongs to the team.

I had taught folks small batches, clear completion rules, integrated quality. Then the date approached and the completion rule became negotiable, the quality concern moved to later, the retrospective action waited behind delivery work. Training pushed one behaviour. The conditions punished it. I had spent a career naming exactly this, fixed date and fixed scope and fixed team, and never actually fixed, because the scope reversed against us far more often than it reversed our way. Every time it came up it came up as commercial necessity, which is to say it arrived as a fact nobody had to own as a choice. I treated it as a team-local process problem, because local process was the only lever I had.

In Ronald Heifetz’s leadership-development terms, technical problems have known solutions inside current authority and expertise. Adaptive challenges require changes in people’s priorities, beliefs, habits, and loyalties. The most common failure of leadership, he writes, is applying technical fixes when the work is actually adaptive. The training was a technical fix. What the date meant was adaptive work.

In 10X Org, Krivitsky et al. argue that the 10% improvement ceiling is no longer enough; what is needed is a step-change redesign of the organisation resulting in a “10X Org.” I wholeheartedly concur. For software-dependent organisations, Krivitsky, Larman, and Flemm’s Org Topologies and Larman and Vodde’s Large-Scale Scrum are, in my view, the most serious attempts at the redesign (not the last word on it): both change who owns what, end to end, rather than how a team runs its meetings. This book addresses the paradigm and identity layer underneath. Some paradigms must change before the most-fit strategies for the necessary organisational redesign can be considered.

The strongest cases in this book look as if they ran the other direction. Marquet’s submarine and the NUMMI line both changed behaviour first and let the thinking follow; Marquet’s own mechanism is named Act Your Way to New Thinking, and the knowing-doing research is blunt that acting produces knowing more reliably than knowing produces acting. Behaviour-first is real, and for the people a leader leads it is usually the cheaper, better test. But the crew’s paradigms followed the new conditions; the captain’s had already moved. Marquet, and Toyota’s managers at NUMMI, were structure-owners who, as I read their cases, had done much of their own paradigm work first, and that is what let them redesign the conditions everyone else then changed behaviour inside. Behaviour-first is rarely the structure-owner’s own escape route, and no one upstream is going to run the experiment on them. When your own new behaviour keeps reverting, edited back to fit the old pattern, you have found what chapter 2 will name an immunity, and that is where this book’s work begins.

Why the ceiling holds

Even if a misfit paradigm were easy to see, it’s hard to shift.

For Robert Kegan and Lisa Lahey, change rarely fails for lack of sincerity or willpower. It fails because we mean two things at once: a sincere commitment to the goal and a hidden competing commitment to self-protection, sustained by big assumptions held as fact. The leader’s paradigm is exactly this kind of immune system. It isn’t weak or sloppy. It is a brilliantly designed protective architecture, built for an organisational context that may not persist for much longer. Kegan and Lahey describe the inspection step as the move from subject to object: the paradigm becomes available for change only when it shifts from being a thing the leader is to being a thing the leader has. Until that shift, the paradigm is invisible from inside.

The world we know⁠—what Beatrice Bruteau, in The Psychic Grid, calls our community conviction system—is one we collectively construct, and few of us can step outside the shared grid alone (if we can even see it). She draws on Dostoevsky’s Grand Inquisitor and Walter Kaufmann’s decidophobe. The Inquisitor is the figure who lifts the burden of deciding for ourselves. He tells us how it is and what we must do, and we thank him for it. For the CEO, the community conviction system is the Inquisitor: the board’s risk tolerance, peer CEOs’ decisions, the industry analysts’ frameworks. The familiar grid lifts the burden of a new paradigm. Any paradigm or framework can become the Inquisitor when the leader obeys it rather than uses it: applies it without examining whether it still fits. By all comparisons, such leaders were doing fine. The competitive floor was just that low… until today.

This is how cognition works, not a moral failing. The leader’s habitual response and the situation it was built to meet had been running as a single coupled system. The historical response was the right response to its conditions. The conditions changed; the response didn’t, because the two were one thing, and one half of it is still catching up.

I don’t pretend to know which paradigms are running you. I don’t pretend to know whether they fit your situation. Your situation determines that, not me. What I can name is the structural difficulty of seeing a paradigm at all, and the cost of failing to see and change it when the conditions have moved.

What AI changes

For specific shapes of task⁠—particularly writing software⁠—frontier-model releases through 2026 have been closing the gap with human knowledge workers rapidly. AI is now past the question of is it ready? and into are we ready? The readiness in question is organisational: the prevailing org design is already out of date.

As Christophe put it: the LLM doesn’t have to be totally correct, it just has to work at least as well as the average human. Every paradigm and org design tuned for managing the average human worker is now under direct competitive pressure from rivals willing to let AI do much of that work at average-human quality and a fraction of the cost.

The cost line is already visible inside the engineering chain. The CFO asks about the ROI of OpEx going to AI. Engineers most fluent with AI-native work, frustrated with the “efficient” bureaucracy in their current org, leave for AI-native competitors and frontier labs paying more. Acquisition conversations now weight the existing code’s readiness for AI. The CTO sees these signals first, the board hears them next, and by the time the question reaches the CEO as a decision to make, the market has already narrowed the options.

Worse, most AI-sourced advice will compound the paradigm problem rather than fix it. Larman’s Laws of Organizational Behavior describe how change initiatives get co-opted: terminology gets overloaded to mean the status quo and displaced specialists become coaches who deliver the false impression that the change has been done. As a result, I’d argue, much of the published corpus on Agile, Lean, and DevOps is consultant-derivative content. When an LLM writes on these topics, it often regresses to the mode⁠—not the truth⁠—and adds a fawning persona that weakens critical thinking exactly where it’s most needed. Deploy agents at scale on that advice and you are taking it from a tool trained on the corpus that codifies the paradigm you need to leave.

In March 2026, researchers writing in Harvard Business Review put leading LLMs through thousands of simulated strategy decisions and found they reliably favour strategies that match fashionable management language rather than the logic a particular situation calls for. They named the output trendslop. Their fixes are prompting hygiene, and prompting hygiene is worth doing. Grounding the model in verified sources⁠—the source-audited retrieval I build and run in my own practice⁠—is my bet on the stronger fix, but only if the sources were selected correctly in the first place, and none of it reaches the paradigm the advice is applied to.

AI doesn’t solve your context-paradigm mismatch. It sells it back to you.

That is the second of three forces. One: AI turns your existing paradigm into the binding constraint, moving the bottleneck from execution⁠—which the tools increasingly handle⁠—to the mental model the organisation was built around. Two, and sharpest: the tool, trained on the consultant-derivative corpus, sells that misfit back to you with affirmation rather than exposing it. The first force makes your paradigm the problem; the second hides it behind a fluent, agreeable voice. Three isn’t another property of the tool, but what the first two leave you holding: the only option left is change at the level of identity, and no technique reaches it in a straight line, which is why no tool, the flattering one included, can do this for you.

The aviation precedent

The aviation version of the ceiling has been visible for decades. On 6 August 1997, Korean Air Flight 801 hit Nimitz Hill on approach to Guam. Two hundred and twenty-eight people died. Gladwell’s popular reading placed the cause inside hierarchical Korean grammar. The NTSB named several causes, among them the captain’s fatigue and Korean Air’s crew training. The deeper variable, as I read it, was the steepness of the authority gradient that preceded the grammar: the first officer and flight engineer questioned the captain about how low the aircraft was on its approach and registered alarm as the cockpit’s automated terrain warnings sounded. Their hints and checks were the form of challenge the gradient permitted; under that gradient, graded escalation was the rational strategy, and it ran out of altitude before it ran out of steps. The first officer’s call for a missed approach came about seven seconds before the aircraft hit the hill. Read from inside the cockpit, they were doing what the system had trained and permitted.

Facing disasters like this, aviation has spent over four decades moderating the authority gradient through Crew Resource Management. The same authority dynamics show up in retrospectives, failed product launches, unspoken concerns about a CEO’s pet project, boardrooms where everyone knew the strategy was wrong and nobody said it directly enough. Aviation couldn’t look away from the lost lives; AI is now making the boardroom toll of obsolete paradigms similarly hard to ignore.

The work that’s needed

The leader needs identity change, not just skill change. In my experience they’ll need more than skilful consulting and advice: company of a particular depth⁠—good developmental coaching among its forms⁠—held within a different community conviction system. The new practice holds until pressure arrives, then gets edited back into the old pattern, the way the completion rule went negotiable when the date approached. Turning that pattern from something you are into something you have is the move from subject to object that Kegan and Lahey describe, and it can’t be run from inside the paradigm you are trying to see.

I borrow the arc of that change from Karla McLaren, who draws on mythologist Michael Meade’s three stages of initiation. Her subject is trauma; mine is the leader’s passage, with the second stage, the ordeal, renamed dissolution, and the third, being recognised and welcomed back, split in two: recognition and reception. She names the structural failure mode: most modern cultures rarely complete the return. People go through the separation and the dissolution and are abandoned at the threshold of coming back. Without the reception, a person cycles between separation and dissolution indefinitely: the loop this book is trying to close.

This chapter is the start of a separation from our dominant paradigm⁠—and identity⁠—in the midst of the transition AI is now laying bare. The dissolution is the sustained contact with what is falling away. The recognition is the moment the leader sees what they had been subject to, often with a coach figure who can stay steady with them through it. What’s left when the frameworks fall away is the reception: a welcoming into a community conviction system where paradigms can be examined, not parroted.

I am offering these paradigm dichotomies as a starting set. While most have been relevant for decades, some may be partly obsolete in months. I don’t list them with the express purpose of changing your mind about them, though that might well be useful. I list them because they are habitual pulls you can already easily recognise and use as practice for the novel contexts AI will keep surfacing.

This week, take last week’s hardest decision and ask three questions of it. What did it optimise for: speed, certainty, control, looking decisive? What did it trade away to get that? And who is carrying that cost now, that you aren’t?

The thing you optimised for without ever feeling it as a choice is the paradigm. (Say you protected your own credibility without once considering you had the option not to. That’s a paradigm running you.) Run the three questions across a handful of decisions and the pattern stops being evidence against you. It shows what’s ready to move.

If naming it is hard, that’s the starting point, not a failure: seeing your own paradigm is the one thing you can’t fully do alone. Chapter 2 is where you practise it.

As Deming put it in a line Krivitsky et al. share in 10X Org: “There is no instant pudding.” This work isn’t fast. We have influence, not control. The next step is to find someone outside the pattern who can be alongside you: a peer group, a developmental coach, a supervisor, anyone who isn’t running the paradigm you are trying to see. Then build the community that will hold you as you emerge. It’s much harder to make the move from subject to object alone, because the thing doing the looking is the thing you are trying to look at.

The work runs in parallel with redesigning the incumbent organisation, possibly replacing it. In my own practice the two are one engagement: I find where the work waits in the delivery data, then mentor and coach the leaders through the changes that follow and work hands-on with their teams. Org Topologies and Large-Scale Scrum, named earlier, set out the structural changes themselves and how they scale with the size of the group.

I agree with Krivitsky et al.: we can’t afford the 10% ceiling any longer.

Come prepared to die: not you, but the paradigm you have been, and the identity built on top of it.

Going Upstream

The 10% ceiling comes from Jerry Weinberg, who set the rule in The Secrets of Consulting. Alexey Krivitsky, Craig Larman, and Roland Flemm revive it, and argue past it, in 10X Org, the book whose central wager, that the 10% ceiling is no longer survivable, this chapter takes as its own. The redesign work I point to lives in their Org Topologies Primer: Strategic Org Design and in Larman and Bas Vodde’s Large-Scale Scrum: More with LeSS. Deming’s “there is no instant pudding” reaches me through the same 10X Org.

The content-versus-affective distinction, and the naming of the consultant’s collusion, are Peter Block’s, from Flawless Consulting: A Guide to Getting Your Expertise Used. The technical-versus-adaptive cut is Ronald Heifetz’s, with Alexander Grashow and Marty Linsky, in The Practice of Adaptive Leadership. The immunity, the competing commitment, the big assumption held as fact, and the move from subject to object that turns a paradigm from a thing you are into a thing you have, is Robert Kegan and Lisa Laskow Lahey’s, from Immunity to Change; chapter 2 stays with it. That acting produces knowing more reliably than the reverse is the finding Jeffrey Pfeffer and Robert Sutton document in The Knowing-Doing Gap, and “Act Your Way to New Thinking” is L. David Marquet’s own named mechanism from Turn the Ship Around!, the submarine case I lean on. The NUMMI counterpart is John Shook’s, from “How to Change a Culture: Lessons from NUMMI” (MIT Sloan Management Review, 2010): change what people do first, and the thinking follows.

The collective version of the trap, the community conviction system, and the Grand Inquisitor who lifts the burden of deciding for us (by way of Dostoevsky, and Walter Kaufmann’s decidophobe), is Beatrice Bruteau’s, from The Psychic Grid. That cognition is enacted, the knower and the known arising together, is the enaction thesis of Francisco Varela, Evan Thompson, and Eleanor Rosch in The Embodied Mind: Cognitive Science and Human Experience. Drift, in the precise sense I use it, is Sidney Dekker’s, from Drift Into Failure. And the arc I borrow for the leader’s passage, separation, ordeal renamed dissolution, and the return most cultures never complete, comes from Karla McLaren’s The Language of Emotions, where she is in turn drawing on the mythologist Michael Meade’s three stages of initiation.

The corollary that AI regresses to the consultant-derivative answer rather than the truth is my own extension of Larman’s Laws of Organizational Behavior; I set it out at length in the LLM-epistemology piece. Two sources I draw on here sit outside the corpus of primary texts behind this book, and I cite them as I met them: Malcolm Gladwell’s reading of Korean Air Flight 801 in Outliers (whose hierarchical-grammar account I push back on, in favour of the authority gradient beneath it), and the March 2026 Harvard Business Review study that named “trendslop“: LLMs favouring fashionable management language over the logic a situation calls for. Christophe Louvion’s one line, the LLM doesn’t have to be totally correct, it just has to work at least as well as the average human, I owe to him directly, in conversation.

A paradigm is what you look through, not what you look at. So the decision you are proudest of this quarter, the AI reorg included, is the one it is hiding from you. You can’t catch that alone, any more than you can see your own eye without a mirror. Chapter 2 hands you the mirror. You run a five-minute diagnostic on a decision you already made, then send it to two colleagues who watched.

I work with CTOs and CPOs at software companies with roughly 25–500 engineers, where the engineers are faster with AI and the business isn’t yet seeing the full value. As the tools take over more of the coding, the bottleneck moves to the beliefs the organisation was built around, and that’s often what I find delaying it. If it’s live for you, book a free 30-minute call at hi.chrisgagne.com and bring the one question that would make it worth your time. If you know a CTO or CPO in that spot, pass this chapter on. If you’d rather read on than talk, the newsletter goes on past chapter 23, monthly, at https://www.linkedin.com/newsletters/come-prepared-to-die-7472144387981062144/

Some book links here are Amazon affiliate links; if you buy through them I may earn a small commission, at no cost to you.

Continue reading: Chapter 2 hands you the mirror: a five-minute diagnostic you run on a decision you already made, then send to two colleagues who watched.