Change and Organizational Transformation
Twice in my career I have interviewed two candidates, in the same search, who both claimed the same transformation. Same company, same years, same program name on both CVs (led the digital transformation of the retail division), and, for one bewildering afternoon, apparently the same achievement, lived twice. It is less rare than you would hope. Large transformations employ hundreds of senior people, every one of them acquires the noun, and a decade later the market contains a small regiment of executives who each, personally, transformed that division.
What separated the two candidates was not the story, both told it well, but a question I have asked in every transformation interview since: what did you decide not to change? One of them looked at me as if I had asked about the weather, and returned to the burning platform. The other paused, and then talked for ten minutes about the three things she had fought to protect, a pricing discipline and a veteran logistics team and a country brand nobody at headquarters valued, and what protecting them had cost her politically. Only one of these people had actually held the ship's wheel. Rebuilders know what they refused to rebuild.
This chapter is about assessing that difference. Its terrain is the most inflated word on the executive CV, its stories are the most rehearsed in the repertoire, and its epistemic hazard, after Chapter 9's attribution problem and Chapter 10's inherited machine and Chapter 11's rigged sample, is this: the borrowed screenplay. Our business culture has spent thirty years distributing a universal narrative template for change (the burning platform, the guiding coalition, the resistance, the triumph), and candidates arrive with their history pre-cut to fit it. You are rarely hearing what happened. You are hearing what happened, edited by the genre.
What it is, and what it predicts
Define the cluster as the capability to alter what an organization is while it continues to operate — distinct from Chapter 9's execution the way rebuilding a ship at sea differs from sailing it hard, and demanding, note well, both at once. Five collectable components. Diagnosis: reading what kind of change the situation actually requires — turnaround, realignment, accelerated growth, or the stewardship that transformation-hungry executives least like to hear prescribed; Chapter 1 put situational misdiagnosis among the leading transition killers, and it starts here. Envisioning and framing: making a future legible and worth wanting — direction-giving, distinct from Chapter 11's lateral persuasion though it borrows the same voice. Readiness and coalition: sponsors secured, sequence designed, early wins engineered as evidence rather than theater — Chapter 11's coalition craft at enterprise scale and multi-year duration. Metabolizing resistance: the component that separates the real practitioners — treating resistance as information about the organization rather than as an enemy formation; we will make this testable below. And pace judgment: the feel for absorption — what the organization can metabolize per quarter, what must be stabilized so the rest can move, and when to stop, which the genre's screenplay never covers because triumph is a terrible place to end a real transformation and the only place to end a scripted one.
What it predicts: the change-oriented family is one of the three meta-categories of leader behavior in the modern taxonomies, with time-lagged studies, the kind that measure the leading before the outcomes, supporting its link to unit adaptation and performance; and from the failure side, transformation mandates are where the derailment data concentrate, because they maximize every relational and political load Chapter 1 catalogued. Evidence grade, plainly: real but thinner and more case-contaminated than execution's or team-building's base, because transformation research leans heavily on retrospective cases narrated by winners, and this book grades accordingly.
And one piece of folklore to bury on arrival, in the Chapter 1 tradition: "seventy percent of transformations fail." The number has been repeated for three decades and audited more than once; its provenance dissolves under inspection, an early reengineering-era guess, laundered through consultancy decks into a law of nature. Transformations fail often; nobody has credibly counted how often; and a book that scores candidates for evidence discipline will not itself citation-launder. What survives the audit is directional and sufficient: changing organizations is hard, mismanaged change is expensive, and the capability to do it well is scarce enough to assess carefully.
How it fakes
The borrowed screenplay itself — the three-act arc, beat for beat: crisis discovered (by the candidate), coalition assembled (around the candidate), resistance overcome (beneath the candidate), results delivered (exeunt to applause). Real transformations are full of weird specifics — the acquisition that interrupted everything, the works council negotiation, the pilot that failed and taught more than the plan; the screenplay is smooth because it was written afterward. Smoothness is the tell. Transformation inflation: the cost program, the ERP rollout, the reorg — retold with the grander noun; ask what was different about what the organization was, before and after, and watch the noun deflate or defend itself. Scale creep: our two-candidates problem — led meaning, on inspection, was employed during; the attribution forensics of Chapter 9 apply with the volume turned up. Resistance as villainy: every resister a dinosaur, every doubt an obstacle — remember this one; the probe architecture turns it into this chapter's sharpest instrument. And the unfinished monument: a career of transformations launched and departed mid-arc, each narrated at its rhetorical peak — Chapter 9's launches-without-landings, in epic dress.
The probe architecture
Layer 1 — standardized stimulus: "Take the transformation you're proudest of. Before anything about what you did — tell me what you found. What was actually broken, how did you know, and what did you decide not to change?" The prompt attacks the screenplay at its weakest points: the genre has no scene for diagnosis-in-detail and none at all for deliberate non-change, so the candidate must leave the script or be seen holding it.
Layer 2 — planned probes: What came first, and why that? Who sponsored it — and what did the sponsorship actually consist of when things got difficult? Which early win was engineered, and for whose benefit? Where did the organization push back hardest, and what did the pushback teach you? When did you slow down — and what told you to?
Layer 3 — verification probes: The before and after, in numbers — what did you watch weekly, and where did it end up? Who above you would confirm the diagnosis was yours and not the strategy deck you inherited? And the one that matters most here: name your most serious resister — would they take my call?
Layer 4 — the disconfirming pair, and this chapter's signature. First: "A change you drove that didn't hold — that the organization spat out after you left, or that you now believe was wrong. What do you know now?" Then: "A resister who turned out to be right. What were they seeing that you weren't?" The second question is the single best instrument I know for this cluster. The candidate who cannot produce a right resister across a career of claimed transformations has told you exactly how resistance was processed — as noise, never as signal — and has failed the metabolizing component in one sentence. The candidate who answers with a name, a position, and what the resister saw — the veteran who knew the pricing discipline was the moat, the country manager who knew the rollout pace would break the Gulf business — is demonstrating the component live, on the hardest material available: their own overruled opposition.
In the room, and only outside it
What shows live is texture against template. The screenplay is smooth; reality has splinters — interruptions, reversals, the thing that worked by accident, the sponsor who wobbled. Probe for splinters and score their presence. The not-changed answer shows live too, and richly: real transformers carry a protected list and the political scars of defending it. And diagnostic capability can be sampled directly at low contamination: late in the interview, sketch a disguised situation — a composite with your client's shape — and ask only what would you want to know first? You are not running Chapter 6's simulation; you are watching whether the diagnostic reflex exists, and the first five questions a real change leader asks are worth an hour of narrated triumph.
What only the outside holds: whether it stuck. The two-years-after test governs this cluster as it governed team-building — a transformation's true tense is not delivered but still there — and the witnesses are the organization's memory: the survivors, the successor, and above all the named resister, this chapter's counterparty and the second ring's most valuable call. Also outside: the dignity data, how the change felt to the changed, which the leader cannot fully know and the led never forget.
Red flags — with their innocent explanations
Serial mid-arc departures. Innocent: private-equity and interim careers are structurally mid-arc — check the mandates before charging the person; some executives are hired precisely for act one. The flag firms up when permanent roles show the same rhythm. All resistance rendered as ignorance. Innocent: some resistance genuinely was, once. The right-resister probe adjudicates; a career-long undefeated record against doubt is not a record, it is an editing choice. The template-perfect telling. Innocent: everyone is media-coached now, and a smooth first telling means little; the test is whether splinters appear under Layer 2, or whether the smoothness goes all the way down. Transformation without a baseline. Innocent: cultural change resists clean metrics, honestly. But even then, real practitioners watched something weekly, and can tell you what.
The reference question
Through the two-level method, with the second ring built for this cluster: a named resister, a survivor from below, the successor if reachable. To the resister — the symmetric question: "You were skeptical of [the change]. Looking back — what did they get right, and what did you get right?" (Answers to this are almost embarrassingly diagnostic: respect between old adversaries is the strongest signal this cluster produces.) To the survivor — frequency: "How often did the plan actually adjust because of what the organization was saying — routinely, occasionally, never?" Calibration, the double form: "If the company had to change again, would you want them leading it? And would the organization want it?" The gap between those two answers, when there is one, is the finding.
Scorecard anchors
2 — Below the bar. Claimed transformations deflate under the noun test into programs; the telling is screenplay-smooth to the bottom; no right resister across a career; no protected list; nothing verifiably survived their departure. The resister ring, where reachable, remembers being managed, not heard.
3 — At the bar. One transformation verified end to end: a diagnosis that was theirs, a coalition that held under strain, an adjustment made because the organization taught them something, a landing confirmed by witnesses; a credible not-changed answer; a resister engaged with respect even if never converted.
4 — Distinguishing strength. The verified pattern, plus the rare marks: the change still standing years later, in the organization's own testimony; a named resister who takes the call and answers the symmetric question with respect; the wrong-change story told with precision about what they misread; the protected list articulated with its political costs; and the diagnostic reflex demonstrated live on unfamiliar material. Rebuilders who know what they refused to rebuild.
The seam with Part IV
Two threads to hand forward. The first: what change means to this person. There exists a recognizable senior figure for whom transformation is not a situational response but a personal necessity — who needs the drama, arrives with the rebuild regardless of the diagnosis, and grows restless in any organization that merely works. That is not a capability deficit; every skill in this chapter may be present at level 4. It is an identity pattern, change as self, and it makes the person magnificent for one kind of mandate and quietly dangerous for every other. The second thread: the candidate's relation to what they inherit. Contempt for the existing organization — for its past, its veterans, its reasons — leaks through transformation stories more than anywhere else, and an executive who cannot honor what a company has been will be resisted by everything in it that remembers. Both threads surface here, neither is scoreable here, and Chapters 20 and 22 are waiting for them. And note the client-side mirror before leaving: the misdiagnosis risk runs both ways, because a board infatuated with the word transformation will hire the screenplay when the mandate needed a steward, and the kindest expensive thing an assessor can do is say so at scoping, which is Chapter 3's job and the reason these chapters keep pointing back to it.
Where the rules run out
The honesty paragraph. This cluster's evidence base is the thinnest of Part III's first four: the change-oriented behavior category is established and the time-lagged support is real, but the transformation literature is dominated by retrospective cases narrated by winners, with survivor bias built into the archive, and the construct's boundaries are soft enough that reasonable assessors will disagree about what counts. The 70-percent folklore is dead but nothing precise replaces it; the anchors are this book's synthesis, unvalidated as a scale; and the over-rotation warning inverts Chapter 9's, because a scorecard tilted to this cluster selects transformation theater for organizations that needed stewardship, which is a client-side failure the assessor is paid to prevent, not decorate. Score the cluster hard when the mandate is real change; weight it honestly down when it is not; and let Chapter 25's log judge the anchors over time.
Notes and sources
Evidence grades: [M] meta-analytic/systematic; [L] peer-reviewed primary; [S] credible practitioner/survey; [A] audited folklore; [T] flagged synthesis/inference.
- Change-oriented behavior as a meta-category; time-lagged support: Yukl's hierarchical taxonomy (2012); DeRue et al. (2011); change-leadership studies with lagged designs. [M/L]
- Situational misdiagnosis as a transition killer; situation typing: transition literature (Watkins's STARS tradition), per Chapter 1. [S/L]
- "70% of transformations fail" — provenance audit and debunking: Hughes, "Do 70 Per Cent of All Organizational Change Initiatives Really Fail?" (Journal of Change Management, 2011). [A]
- The narrative template: Kotter's change model as cultural script (used here as an object of analysis, not as evidence). [S]
- Attribution and scale creep: Chapter 9's forensics sources (Groysberg; Kaplan tradition). [L]
- Resistance as information: readiness and resistance research (Armenakis tradition; recipient-perspective change literature). [L]
- Faking forms and coached narratives: Levashina & Campion; ATIC — Chapter 5's sources. [L/M]
- The right-resister probe, the not-changed instrument, the noun test, five-part packaging: this book's synthesis from practice. [T]