Leading Change
People do not resist change; they resist loss — so the first document of any change program is not the plan but the ledger of who pays for it, written in their words rather than yours.
From the Founder
There is a sentence I had to learn the hard way and I will give it to you free: sometimes you cannot bring everybody along. I spent years believing that if I explained well enough and listened long enough, everyone would eventually come. Some will not. Some are losing something real, and no framing changes that arithmetic. I have held positions that cost me relationships — people who stopped speaking to me over what I believe. I am at peace with it, because the alternative was letting the room decide what is true. Be careful here, though. Deciding you cannot bring everybody is not permission to stop being charitable. Common ground first, then context and evidence, then the point. You owe every person the honest case and the dignity of hearing it from you directly. What you do not owe anyone is a change you know is right, delayed forever because someone has not agreed yet.
Executive Summary
Organizations do not resist change; they resist loss, and the losses are concentrated while the gains are diffuse and delayed. This lesson gives you the Loss Ledger — the document you write before the announcement, naming who pays and in whose words. You will work Nehemiah's rebuilding as a change program with a predictable opposition sequence, including the chapter where the trouble comes from inside; the Jerusalem Council as institutional change handled by process rather than fiat; Burke steelmanned properly against Paine; Machiavelli on the innovator's asymmetric coalition; and an honest accounting of why Kotter is a practitioner checklist rather than a finding. It ends in sequencing: coalition before announcement, and why the reverse is how mayors lose their agenda.
Learning Objectives
- Reframe resistance as loss rather than irrationality, and build a Loss Ledger before any change is announced
- Trace the opposition sequence in Nehemiah 2-6, including internal grievance, and contrast it with the process-based institutional change of Acts 15
- State honestly which change-management claims are empirical and which are practitioner frameworks, including Kotter's eight steps and the unsourced 70-percent-failure statistic
- Sequence a change program so that coalition precedes announcement, and identify what a chief executive can and cannot do unilaterally
Teaching Manuscript
Nobody Resists Change
Lesson 7.6 ended with the first red number and what you do with it. Assume you built the system and the truth is now arriving. Congratulations — you have earned a harder problem. The truth is telling you that something has to change, and changing it will turn out to be an entirely different discipline from finding out about it.
Start by throwing out the phrase everyone uses. There is no such thing as resistance to change. People change constantly and voluntarily — they move, marry, switch careers, learn instruments, uproot their families for opportunity. What they resist is loss. Every time you have watched a sensible team dig in against an obviously better system, you were watching people protect something the proposal was quietly taking from them: status, expertise that took a decade to build, a route to promotion, an identity as the person who knows how this works. Call it resistance and you have diagnosed irrationality and pointed yourself toward more explaining. Call it loss and you have diagnosed it as a transaction, and transactions can be negotiated.
The behavioral research supports the reframe, with the honesty this academy requires. Kahneman and Tversky's prospect theory, published in Econometrica in 1979, established that losses loom larger than equivalent gains in how people evaluate prospects — a finding replicated extensively in laboratory settings. Related work on the endowment effect finds that people demand more to give up a thing than they would have paid to acquire it. I will flag the live dispute rather than hide it, and state it precisely rather than softened: Gal and Rucker's 2018 review is not merely a magnitude critique. They argue that many of the classic demonstrations confound loss-versus-gain framing with a separate variable — giving something up versus acquiring it — and that the loss-looms-larger asymmetry shrinks or, in some designs, disappears once the two are pulled apart. That challenges the general claim itself, not just its size, and other researchers have pushed back on their reading of the evidence. Treat loss aversion as well-supported in many specific contexts and genuinely contested as a universal law — do not bank on a fixed multiplier in every proposal you write, and do not assume the asymmetry is automatically running against you until you have checked whether this change is actually experienced as a loss rather than a foregone gain.
So name the framework, and this one is a document rather than a mindset. The Loss Ledger has four columns and you write it before you announce anything. Column one: every group affected, and what each one loses — written in their words, not yours. If your version of what the night-shift supervisors are losing does not match what a night-shift supervisor would say, you have not written a ledger, you have written a defense. Column two: whether the loss is material or status-based, because they need different responses and confusing them is expensive. Column three: whether you can compensate it, sequence it so it lands later or lighter, or must simply pay it and say so. Column four, and this is the one leaders skip: who you cannot bring along, and how you will treat them anyway.
That fourth column is where most of the character of this lesson lives. Some changes genuinely cost some people something you cannot give back. A consolidated office means somebody's commute doubles. An honest budget means a program somebody built their career on ends. You can be humane, generous, early and direct about all of it, and they will still lose. Pretending otherwise — talking about opportunity and growth when a person is looking straight at a loss — insults their intelligence and destroys the trust you will need for the next change. Say the true thing: this costs you, here is why we are doing it anyway, here is what I will do for you, and here is what I cannot do.
Nehemiah's Opposition Was On Schedule
Module 6 used Nehemiah for vision and Module 5 used him for influence without authority. Neither touched what I want here. Read Nehemiah 2 through 6 as a change program under fire and you find something close to a schedule — a sequence of opposition types that arrives in a predictable order, which means it can be anticipated rather than merely survived.
It opens with ridicule. Sanballat, Tobiah and Geshem mock and despise the project before anyone has laid a stone. Ridicule is the cheapest form of opposition and the most underestimated; it costs the opponent nothing and works on the marginal supporter who has not yet committed. Then it escalates to anger and public derision as the wall actually rises, because a project that is failing needs no opposition. Then to conspiracy — chapter 4 has the adversaries plotting an actual attack, and Nehemiah's response is instructive: he posts a guard and keeps building, with the workers carrying loads with one hand and a weapon with the other. He neither ignores the threat nor lets it become the project.
Then comes the part every executive should study hardest, because it is the part nobody expects. Chapter 4 records the internal collapse of morale — the strength of the burden bearers failing, too much rubble, the work too large. And chapter 5 records something worse than fatigue: the change program itself was generating injustice inside the coalition. The people cried out that they were mortgaging fields and vineyards and selling their children into servitude to survive, and that the nobles among their own people were exacting interest from them. Nehemiah's response was to confront his own side publicly and require restitution. Register what happened. Halfway through a project under external attack, the leader disciplined his own coalition, at the risk of splitting it, because the project had begun to cost his own people unjustly. Most leaders will not do this. They will tell themselves that the mission requires unity right now and the internal problem can wait until after — and the internal problem is precisely what kills the change. Only after chapter 5 does chapter 6 bring the personal attacks: four invitations to a meeting at Ono that Nehemiah refused with a line worth memorizing, "I am doing a great work and I cannot come down" (Neh. 6:3, NASB 1995), then an open letter of slander, then a hired prophet trying to lure him into a discrediting act. The wall was finished in fifty-two days.
So run the taxonomy against your own situation. External ridicule, external threat, internal exhaustion, internal injustice, and finally personal targeting of the leader. If you are three weeks into a change and encountering ridicule, you are not failing; you are on schedule. If you are three months in and morale is sagging, that is the burden bearers, and the fix is visible progress and rest, not a speech. And if your change program has started producing injustice inside your own coalition — if the people carrying it are quietly bearing costs you have not acknowledged — stop and fix that before you deal with any external opponent, because Nehemiah 5 is the chapter that ends change programs.
Set beside it a different model for a different problem. Acts 15 records the early church's hardest institutional question: whether Gentile converts had to be circumcised and keep the law of Moses. This was not a project with opponents; it was a genuine dispute inside the community about what the community was. And it was handled by process rather than fiat. The apostles and elders convened. There was, in Luke's account, much debate. Peter testified from experience, Barnabas and Paul reported what had happened among the Gentiles, and James rendered a judgment anchored in Scripture. The decision went out in writing — "For it seemed good to the Holy Spirit and to us to lay upon you no greater burden than these essentials" (Acts 15:28, NASB 1995) — and was carried by named delegates who delivered it in person rather than by letter alone. Note the honest caveat: interpreters differ on how Acts 15 relates chronologically to the Antioch episode in Galatians 2; I am not resolving that here. The point still stands. When the question is what we are, process is not a delay tactic. Process is the legitimacy that makes the outcome hold after the room empties.
Burke Steelmanned, Machiavelli Verified
Edmund Burke gets conscripted into every argument against doing anything, usually by people who have not read him. Steelman him properly, because his actual position is more useful than his reputation and considerably harder to answer.
Burke was not opposed to change. He argued for conciliation with the American colonies, worked for relief of Irish Catholics, and spent years prosecuting the impeachment of Warren Hastings for the conduct of the East India Company in Bengal. His line in Reflections on the Revolution in France is not a defense of stasis but its opposite: a state without the means of some change is without the means of its conservation. His argument is epistemic. Institutions encode accumulated practical knowledge that no individual reasoner possesses — the reasons for a rule are frequently lost while the rule remains load-bearing. Therefore reform should proceed by repair with reference to what exists, at a pace that allows error to be detected and corrected, rather than by demolition on the authority of a theory. Applied to your organization: the process you find absurd may be absorbing a failure mode nobody remembers, and the fastest way to find out is to remove it and wait.
Now the counter-steelman, because Burke can be a permanent excuse. Thomas Paine's reply in Rights of Man makes the case that the dead cannot govern the living, that prescription is simply injustice with a long tenure, and that Burke's prudence has a habit of arriving exactly when the beneficiaries of the existing order need it. That charge lands. Gradualism has been the most respectable argument for delay in the history of every injustice eventually ended, and the people asked to wait were never the ones making it. Hold both. Burke is right that you rarely understand a system as well as you think you do. Paine is right that some arrangements do not deserve careful preservation while their victims wait for your caution to mature. Which one governs a given case is a judgment, and judgment is what you are being paid for.
Machiavelli supplies the coalition arithmetic. In chapter six of The Prince he argues that there is nothing more difficult to undertake, more doubtful of success, or more dangerous to manage than initiating a new order of things — because the innovator has as active enemies everyone who did well under the old order, and only lukewarm defenders among those who might do well under the new. And he gives the reason for the lukewarmness, which is the part usually left out: the potential beneficiaries are restrained partly by fear of the adversaries, who have the law on their side, and partly by the incredulity of people who do not genuinely believe in anything new until they have had actual experience of it. Translations differ in wording; that is the substance of the argument.
Read that against the Loss Ledger and you get the real problem. It is not that your opponents outnumber your supporters. It is asymmetric intensity. The people losing something specific know exactly what it is and will organize this week. The people who will gain something diffuse and future do not yet believe it and will not show up until it has already happened. Every failed change program you have watched died in that gap. Which tells you what the sequencing has to accomplish: give your beneficiaries something concrete early enough that their belief becomes experience, and give your losers a hearing early enough that their intensity is spent on negotiation rather than mobilization. Name the two groups in your own situation. Who loses something specific this quarter, and who gains something vague in two years? Now you know where the work is.
Without scrolling back: name the four columns of the Loss Ledger, and say which chapter of Nehemiah shows the opposition coming from inside the coalition.
What the Change Literature Can and Cannot Claim
The change-management shelf is enormous and its evidentiary foundation is thin. Know which is which before you build a plan on any of it.
John Kotter's eight steps — establish urgency, form a guiding coalition, develop a vision, communicate it, empower action, generate short-term wins, consolidate gains, anchor the change in culture — came out of his observation of roughly a hundred organizations, published as an article in 1995 and as Leading Change in 1996. Label it correctly: it is a practitioner framework derived from case observation, not a tested causal model. No controlled study established that the eight steps in that order produce successful change, and the sequence has never been isolated from everything else those companies were doing. It is a good checklist. It is not evidence, and when someone puts it on a slide as though it were, say so.
While we are here, kill a statistic. You will hear that seventy percent of change efforts fail. That number has been repeated for decades and traced by researchers back through citation chains that do not terminate in any study establishing it. It is folklore with a decimal point. Kurt Lewin's unfreeze-change-refreeze is likewise a model, never a demonstrated mechanism, and the proprietary frameworks sold with certifications are consultancy intellectual property rather than science. Reviews of the organizational change literature have repeatedly noted the same two problems: the field's most-cited models were not derived from controlled research, and the outcome evidence is weak.
So what does have support? Procedural justice, and it is the most useful finding in this lesson. A large body of organizational justice research — Colquitt and colleagues' meta-analysis covering twenty-five years of it is the standard reference — finds that people's acceptance of outcomes depends substantially on whether they judge the process that produced them to be fair, and that procedural fairness carries independent weight beyond the favorability of the outcome itself. Read that in plain executive language: people will accept a decision they dislike if they had a genuine hearing, understood the reasoning, were treated with respect, and saw the rule applied consistently. That is not a communication technique. It is a set of things you either did or did not actually do. The participation research points the same direction, though the classic studies are methodologically limited and should not be oversold.
There is an ethical edge on this that I want stated plainly, because procedural justice is the most abusable finding in the leadership literature. If you run consultation you never intended to be influenced by, you have not bought legitimacy; you have bought a delay and a betrayal. People detect theater, and they detect it after investing effort, which is when it does maximum damage. The honest version is cheaper and works better: tell people what is genuinely open and what is already decided. "The decision to consolidate is made. How we sequence it, who moves when, and what we do for people whose commute changes are open, and I want your input on those." That sentence costs you nothing you actually had, and it is the difference between consultation and a survey nobody believes.
Sequencing, and the First Ninety Days of a City
New York offers a matched pair on the same subject, thirty-three years apart. After the Ocean Hill-Brownsville conflict and the teacher strikes of 1968, the state legislature enacted school decentralization in 1969, creating community school boards and dispersing authority away from a central board. In 2002 the legislature moved the other direction entirely, granting the mayor control of the school system, abolishing the old Board of Education and creating the Department of Education and the Panel for Educational Policy. Same domain. Opposite structural theories. Both sold as the reform that would fix accountability.
The honest reading is uncomfortable for anyone who loves a structural fix. Governance change is a necessary condition for some improvements and a sufficient condition for none. Under mayoral control, graduation rates in the city rose considerably over the following decade — and the causal question is genuinely contested, because state graduation standards and testing regimes changed during the same period, credit-recovery practices drew scrutiny from investigators, and disentangling governance from everything else in those years is work the Research Alliance for New York City Schools and the Independent Budget Office have taken seriously and press accounts have not. Cite the researchers, not the headline. And notice the political fact underneath: mayoral control is not a permanent grant. It has required periodic reauthorization in Albany ever since, which means a mayor's central education authority is a lease, not a deed. A candidate who does not know that will promise things he cannot deliver.
That leads to the sequencing rule. Build the coalition before the announcement. Not because it is more polite, but because of what an announcement does mechanically. It converts a negotiable proposal into a fixed public position, which triggers everything Module 5 taught you about commitment and consistency — now working against you, because the moment your opponents state a public position they are locked into defending it. It activates every losing constituency simultaneously, which is the only way they can coordinate. And it hands your opponents the framing window, because they will be describing your plan to their people before you have finished describing it to yours. The mayors who lose their agenda in year one usually lose it this way: a bold announcement in week three that unifies opposition, hardens the Council, and produces a retreat that costs more authority than the original proposal was worth.
So what does the sequence look like? Before the announcement: write the Loss Ledger, then take it to real people in each affected group and let it change. Find the beneficiaries who can testify from experience rather than hope and give them something concrete early. Secure the votes or the authority you will actually need — in a city that means knowing which of your objectives requires only executive action within existing law, which requires local legislation from the Council, which requires Albany, and which runs through a fixed statutory clock like the land use review process or the Charter's budget calendar. Then announce, with the price named out loud and the losers named to their faces first rather than left to learn it from a press conference. And be honest about the boundaries of the office while you do it: the MTA is a state authority and no mayor runs it; school governance depends on Albany's reauthorization; the district attorneys and the courts are independent. Promising a change outside your authority is not ambition. It is the first broken promise of the administration, made before you take office.
Do not confuse the change you can order with the change you must lead. You can order a reorganization, a budget cut, a new reporting line — those execute on signature. You cannot order a culture, a standard of care, or a new way of making decisions, and every executive who has tried has produced compliance and called it transformation. Ronald Heifetz's distinction between technical problems, which existing expertise can solve, and adaptive challenges, which require the people themselves to change what they value and how they work, is the cleanest statement of the difference. Technical work is done to an organization. Adaptive work is done by it, and your job is to hold the group in the discomfort long enough for them to do it — slower and lonelier than signing an order. Now go write the ledger, and carry the fourth column into 7.8, where we ask whether the person running all of this is being managed by anyone at all.
In one sentence: what is the difference between how you should cite Kotter and how you should cite the organizational justice research?
Through the Six Lenses
Evidence levels labeled per the Truth & Intellectual Integrity standard.
Biblical
Nehemiah 2-6 reads as a change program with sequenced opposition: ridicule (2:19), derision and conspiracy as the wall rises (ch. 4), internal exhaustion, then internal injustice — nobles exacting interest from their own people (ch. 5), confronted mid-build at risk to the coalition — and finally personal targeting (ch. 6), refused with "I am doing a great work and I cannot come down" (6:3, NASB 1995). Acts 15 models the other mode: an institutional question settled by convening, debate, testimony, scriptural judgment, a written decision and named delegates.
Philosophical
Burke is not anti-change — he sought conciliation with the colonies, relief for Irish Catholics, and Hastings's impeachment, and argued in Reflections that a state without the means of some change lacks the means of its conservation. His case is epistemic: institutions hold practical knowledge no reasoner can reconstruct. Paine's reply in Rights of Man is the counterweight: the dead should not govern the living, and prudence reliably serves whoever benefits from delay. Machiavelli, Prince ch. 6, supplies the arithmetic — committed enemies, lukewarm defenders restrained by fear and by disbelief in anything not yet experienced.
Scientific
Prospect theory (Kahneman & Tversky, Econometrica, 1979) established in laboratory settings that losses weigh more heavily than equivalent gains; the endowment effect extends it. Gal and Rucker (2018) go beyond a magnitude critique: they argue many classic demonstrations confound loss/gain framing with an action/inaction confound, and that the asymmetry itself — not only its size — weakens or disappears once separated, a reading other scholars dispute. Treat loss aversion's generality as contested, not merely its field magnitude. Organizational justice research, including Colquitt and colleagues' meta-analytic review, robustly finds that procedural fairness independently predicts acceptance of unfavorable outcomes. Kotter's eight steps and Lewin's unfreeze-change-refreeze are practitioner frameworks from observation, not tested causal models, and the ubiquitous 70-percent-of-change-fails figure traces to no study establishing it.
Historical
New York moved school governance in opposite directions on the same rationale: decentralization enacted by the state legislature in 1969, then mayoral control in 2002, abolishing the Board of Education and creating the Department of Education and the Panel for Educational Policy. Graduation rates rose in the following decade, but standards, testing and credit-recovery practices changed alongside; causal attribution is contested and belongs to the Research Alliance for New York City Schools and the Independent Budget Office, not press accounts. Mayoral control has required periodic Albany reauthorization since — a lease, not a deed.
Influence
An announcement is a commitment device pointed the wrong way: Cialdini's commitment-and-consistency research predicts that once opponents state a public position they will defend it beyond its merits, so every day of premature publicity buys hardened opposition. Consult before you announce, and disclose honestly what is open versus decided. The ethical line from Lesson 5.1 governs: consultation you never intended to be influenced by is manipulation, and it is detected after people have invested effort — which is the moment it does the most damage.
Executive
Sequence: Loss Ledger, then real conversations with affected groups, then early concrete wins for beneficiaries, then secured authority, then announcement with the price named. Know which objectives need only executive action within existing law, which need Council legislation, which need Albany, and which run on fixed statutory clocks such as land use review or the Charter budget calendar. Heifetz's technical-versus-adaptive distinction sets expectations: reorganizations execute on signature; culture and standards of practice do not, and ordering them produces compliance mislabeled as transformation.
Case Study
New York City, 1975: Solvency Bought With Concentrated Losses
SITUATION. By spring 1975 the city could no longer roll over its short-term debt. Years of funding operating expenses through borrowing and shifting costs into the capital budget had left books no underwriter would stand behind. CONSTRAINTS. The change was not the mayor's to lead; Abraham Beame had been comptroller while the practices accumulated. Any fix required imposing concentrated losses on organized constituencies during a recession. DECISION. The state created the Municipal Assistance Corporation in June 1975, then the Emergency Financial Control Board under the state Financial Emergency Act for the City of New York (1975), which took control of the city's budget and labor contracts. Elected leadership traded budgetary autonomy for solvency; the city adopted generally accepted accounting principles, cut headcount, froze wages, and CUNY began charging tuition in 1976. ANALYSIS. Structurally it worked, producing budget-monitoring institutions still operating. Politically it ruined those who carried it: the losses were concentrated and immediate, the gains diffuse and years away. The fiscal restoration is not disputed; the distribution of its costs is argued to this day, with advocacy groups such as the Community Service Society — label the perspective — contending they fell hardest on the poorest neighborhoods. DISCUSSION. When the change you believe in requires someone to lose something real, will they hear it from you first, or find out afterward?
Reflection Questions
- Take the change you most want to make. Write what the person who loses most would say they are losing — in their words. Then ask them, and compare the two versions.
- Where in your current program are your own people quietly bearing an unjust cost you have not acknowledged? That is your Nehemiah 5, and it will end the change before any opponent does.
- Which is the greater risk in your situation right now: Burke's error of demolishing a system whose function you did not understand, or Paine's charge that your caution is serving whoever benefits from delay?
- Name one consultation you have run — or are planning — where you were never genuinely open to being influenced. What will you do about it before people figure it out?
Practical Exercise — The Loss Ledger
Choose a real change you intend to lead. Build a four-column table. Column one: every affected group. Column two: what each loses, written as that group would state it — and then verify at least three of the entries by asking an actual member of the group, and correct what you got wrong. Column three: material or status loss, and whether you can compensate it, sequence it, or must simply pay it. Column four: who you cannot bring along, and precisely how you will treat them anyway — the conversation, who has it, when, and what you will offer. Then write two dates at the bottom: the date you will finish the pre-announcement conversations, and the date you will announce. If the second date comes first, you have found your problem before it found you.
Assessment
This Week’s Commitment
Take the change you are currently contemplating. Before you announce anything, name the three groups who lose most, schedule a conversation with a real person in each group within ten days, and write down — in advance — the one concession you are genuinely willing to make and the one you are not.
Identity statement to carry this week: “I will not disguise the price of a change I believe in. I will name who pays, say it to their faces before they hear it elsewhere, and I will not need everyone's agreement in order to do what is right.”
Discussion Questions
- Is there a defensible version of gradualism that is not simply delay serving the people who benefit from the status quo? What would distinguish the two in a case you know?
- Nehemiah confronted his own coalition in the middle of the build. When is that right, and when is it a leader indulging a principle at the mission's expense?
- A leader tells you a change is non-negotiable but invites feedback on implementation. Is that honest sequencing or managed consent, and what would you look for to tell the difference?
Reading List
- Nehemiah 2-6; Acts 15:1-31 (NASB 1995)
- Edmund Burke, Reflections on the Revolution in France (1790)
- Thomas Paine, Rights of Man (1791) — the reply Burke must be read against
- Niccolo Machiavelli, The Prince, chapter 6 — on introducing a new order
- John Kotter, Leading Change (1996) — practitioner framework, read as a checklist
- Daniel Kahneman & Amos Tversky, 'Prospect Theory: An Analysis of Decision Under Risk,' Econometrica 47 (1979)
- Ronald Heifetz, Leadership Without Easy Answers (1994) — technical versus adaptive work