Leading Change

1. 1Complete stages 1-4 first: high urgency, a powerful guiding coalition, a clear vision, and communication that reaches employees. These already remove much disempowerment before you attack specific barriers.
2. 2Diagnose which of the four barriers is live: structures, skills, systems, or supervisors. Do not assume the obstacle is external—some roadblocks exist only in people's heads, and there the task is to convince them no external barrier exists.
3. 3Attack structural barriers: eliminate narrow job categories that undermine productivity or customer service, and realign the org design so it fits the change vision rather than fighting it.
4. 4Fix systems that force people to choose between the new vision and their self-interest—especially compensation, performance-appraisal, and human resource systems. Retire the ones that reward old behavior.
5. 5Provide the training that gives employees the skills the new vision demands, so willing people are not blocked by incapability.
6. 6Confront obstructive supervisors early through honest dialogue, not political maneuvering: lay out the industry, the company, the vision, the help you need, and the time frame, then ask 'What can we do to help you help us?'
7. 7Read the outcome of that dialogue: if the person is willing but blocked, solve the block; if willing but incapable, use the clear expectations and timetable to make eventual removal less contentious; if hopeless, that becomes clear early and you replace them.
8. 8Watch behavior, not just words—especially your own and other important people's. Deeds are the more powerful form of communication, and inconsistent behavior by senior figures undermines everything else.

Ralph, nicknamed 'The Rock,' was the number-three executive at a major financial services company. He paid lip service to the firm's change efforts but never altered his own behavior or pushed his managers to change; he refused to reward the ideas the new vision called for and let human resource systems stay intact even when they clearly contradicted the new ideals. He acted this way because he didn't believe major change was needed and feared he couldn't deliver both change and expected operating results—and he got away with it. One well-placed blocker like Ralph can stop an entire change effort, because he was not in just any management job. The remedy the passages endorse is honest dialogue confronting him early, not a slow, sleazy-looking political strategy to contain him. Executives who avoid this later say, 'I should have dealt with Hal/George/Irene much earlier.'

• If the barrier is only in people's heads, then convince them no external obstacle exists rather than restructuring anything.
• If compensation or appraisal systems force people to choose between the vision and self-interest, then change the system—willpower will not survive misaligned incentives.
• If a supervisor is willing but feels blocked, then solve the block; if willing but incapable, then set clear expectations and a timetable; if hopeless, then move to replacement, which honest early dialogue usually reveals quickly.
• If you catch yourself building a complicated political strategy to contain a blocker, then stop and switch to honest dialogue—covert tactics are slow and look terrible in daylight.
• If an important individual's deeds contradict the verbal message, then treat that as the priority fix, because behavior is the more powerful form of communication.

• Delaying confrontation of a problem manager out of guilt, political concern, or fear for short-term results. The tell: you keep saying 'I should have dealt with him much earlier.'
• Letting one well-placed blocker survive. The tell: other employees see he isn't confronted, become discouraged, stop producing short-term wins, and give up before the finish line.
• Communicating the vision in words while behaving inconsistently. The tell: employees quietly conclude leadership is 'a bunch of hypocritical jerks.'
• Using authoritarian decree or micromanagement to force behavior change. The tell: people ignore you or pretend to cooperate while undermining you, or change comes only incrementally and deadly slow.
• Treating all obstacles as external and restructuring when the barrier was psychological, or ignoring real structural/system barriers and blaming employees who 'embrace the vision but feel disempowered.'

• ▸Change vision (one line): the direction employees are trying to implement
• ▸Structural barrier: which job categories or org design block the vision, and the redesign
• ▸Skill gap: what capability employees lack and the specific training to close it
• ▸System misalignment: which compensation/appraisal/HR system rewards old behavior and how you'll change it
• ▸Obstructive supervisor: name and what demand or behavior contradicts the transformation
• ▸Dialogue script: industry + company + vision + help needed + time frame, ending in 'What can we do to help you help us?'
• ▸Diagnosis result: willing-but-blocked / willing-but-incapable / hopeless
• ▸Action + owner + date: the committed next step and who is accountable
• ▸Behavior check: which important person's deeds must change to match the verbal message

1. 1Distinguish creating from hoping: treat short-term wins as an active management task, not a passive expectation that 'good things will happen' over time.
2. 2Set explicit performance goals inside the yearly planning system so wins are committed to, scheduled, and owned — not left to chance.
3. 3Scope the win to land within six to eighteen months and select improvements that are visible and unambiguous — a measurable financial or operational result skeptics cannot dismiss.
4. 4Deliberately pick early projects that produce results the toughest audience will accept (e.g., the divisional controller who wants a big dip in inventories or an offsetting financial benefit), not just internal milestones like models built or software written.
5. 5Sequence wins across the wheels-within-wheels structure: run a small early project through all eight steps to completion so a finished, celebratable result appears while larger efforts are still mid-stream.
6. 6Achieve the objective, then reward the people involved with recognition, promotions, or money — make the win and its authors publicly visible.
7. 7Use the commitment to produce a short-term win as pressure that keeps urgency and complacency in check when the larger quality or cultural effort is known to take a long time.

Nelson, a 'big ideas' person, developed with two colleagues a vision for how his inventory control (IC) group could use new technology to radically reduce inventory costs without risking stock outages. They implemented for a year, then two, and by their own standards accomplished a great deal: new IC models developed, new hardware purchased, new software written. By the standards of the divisional controller — the skeptic who wanted a big dip in inventories or some other financial benefit to offset the costs — they had produced nothing. When questioned, they explained that big changes require time; the controller accepted that for two years, then pulled the plug. The failure was not the vision but the absence of a deliberate, unambiguous performance win inside eighteen months that would have offset costs and bought continued support. Contrast this with a medium-to-large telecom whose six-year transformation showed early visible results at six to twelve months while the biggest payoff came near the end — because smaller projects were completed early rather than deferred.

• If a win can't be pointed to within six to eighteen months, then too many employees will give up or join the resistance — re-scope for an earlier, visible result.
• If your reported progress is all activity (models, hardware, software) and none of it satisfies your toughest skeptic's financial or operational test, then you have milestones, not wins — pick a different target.
• If the effort is known to be long (quality or cultural change), then plant explicit short-term commitments precisely to stop urgency from dropping.
• If a win lands, then reward its people with recognition, promotions, or money — otherwise you forfeit the reinforcement the win exists to provide.
• If you're merely assuming good things will happen or are absorbed in the grand vision, then you're hoping, not creating — install goals in the yearly planning system now.

• Confusing effort with results: the tell is a defense like 'big changes require time' offered when skeptics see no financial benefit — as with Nelson's team.
• Getting so caught up in a grand vision that no one worries about the short term; the tell is that no short-term goals exist in the planning system.
• Passive hoping instead of active pursuit; the tell is the absence of any named owner, deadline, or committed metric for an early result.
• Choosing wins your hardest audience won't count; the tell is internal celebration while the divisional-controller equivalent still says you've produced nothing.
• Letting urgency drift on a long program; the tell is momentum loss and the phrase 'let's get on with it' giving way to disengagement once people sense the march has no near-term checkpoints.

• ▸Win statement: the specific, visible performance improvement in one sentence
• ▸Deadline: the target date, within six to eighteen months
• ▸Skeptic test: the exact result your toughest audience (e.g., the controller) will accept as real
• ▸Metric and baseline: the number that must move and where it starts
• ▸Owner: the individual accountable for delivering it
• ▸Planning-system entry: where this goal is recorded in the yearly plan
• ▸Link to vision: one line connecting the win to the overall change effort
• ▸Reward: the recognition, promotion, or money given on achievement

1. 1Sequence deliberately: get well into urgency (#1) and a powerful guiding coalition (#2) before you chase wins, because a weak base makes momentum die 'far short of the finish line.' Skipping steps builds no natural development and feels contrived.
2. 2Actively engineer short-term wins rather than hoping for them: look for clear performance improvements, write them into the yearly planning system, hit them, and reward the people involved with recognition, promotions, or money.
3. 3Target visible results inside the six-to-eighteen-month window. Most people won't stay on the long march without compelling evidence within that span that the journey is producing expected results.
4. 4Choose wins that are credible and unambiguous — the kind neutrals and skeptics cannot dismiss — so each one converts fence-sitters and adds power to the coalition.
5. 5Feed continued urgency alongside wins: keep bombarding people with information about problems, potential problems, and competitive threats so accumulating force does not slide into complacency.
6. 6Use each win as fuel to consolidate gains and launch a larger project — run change as 'wheels within wheels,' where finished small pieces free credibility to start bigger ones.
7. 7Refuse the premature victory celebration: after a win, name what is still unfinished, keep the troops at the front, and confront resisters who declare the war over.

In a medium-to-large telecommunications company, a six-year effort to significantly increase competitive position ran as projects within projects. By the third year the transformation was centered in steps 5, 6, and 7, while one relatively small reengineering project was nearing the end of stage 8 — an early, concrete win. Simultaneously a corporate-staff restructuring was just beginning in steps 1 and 2, and a quality program was moving along behind schedule. Early results were visible at six to twelve months, which sustained belief, but the biggest payoff didn't come until near the end of the whole effort. The finished reengineering piece supplied the credibility to keep the larger, still-immature projects alive. Momentum here was not one event but a staggered chain of wins carrying the effort past inertia toward its largest payoff.

• If no compelling win has appeared within six to eighteen months, then treat it as a momentum emergency — employees will give up or join the resistance.
• If you can only 'hope' a good thing will happen rather than name the goal, timeline, and reward, then you have no short-term win yet — make it active or don't count on it.
• If urgency has fallen and complacency is creeping back, then re-inject problem information before launching the next project, because wins alone won't overcome inertia.
• If initiators want to declare victory, then check whether the change has become 'the way we do things around here' — if not, keep pushing and deny the celebration.
• If a leader like Ralph refuses to confront an obstacle or resister, then treat it as active disempowerment that will slow the effort to a crawl, and escalate.

• Being a 'big ideas' person who plugs away at a grand vision for a year or two with no near-term milestone — the tell: real internal accomplishments but no result outsiders recognize as a win (Nelson's IC group).
• Hoping for wins instead of engineering them — the tell: no goals in the yearly planning system and no rewards attached; managers assume good things will just happen.
• Declaring victory too soon — the tell: enthusiastic initiators go overboard, resisters join to call the war over, weary troops go home, and traditions creep back.
• Building on a weak base by skipping stages — the tell: fuzzy vision makes it hard to target credible wins, empowerment gets sabotaged, and the effort teeters after an illusion of progress.
• Cutting the effort off prematurely — the tell: consultants accomplish something over a few years, then the work is stopped before it sticks and leaves 'hard to find any trace' later.

• ▸Change project name: the specific initiative this win belongs to
• ▸Current stage (1-8): where this project sits in the eight-step process
• ▸Base check (urgency + coalition strong? Y/N): confirm the foundation before chasing the win
• ▸Targeted win: the specific, visible, unambiguous performance improvement
• ▸Deadline (within 6-18 months): the date evidence must appear
• ▸Planning-system entry: where this goal is written into the yearly plan
• ▸Reward tied to it: the recognition, promotion, or money for the people involved
• ▸Urgency refresh: the problem/threat data you will circulate to prevent complacency
• ▸Next-larger project this win enables: how the credibility gets reinvested

1. 1Do this step last, not first: culture shifts at the end of a transformation, not the beginning, so anchor only after new behaviors have demonstrably produced results. Attempting to change norms before results exist gives you nothing to point to.
2. 2Make the results-behavior link explicit and repeated. For each performance improvement, state out loud which specific behavior or attitude produced it — 'sales rose because we put the customer first,' not 'sales rose.' Do not leave people to draw their own connections.
3. 3Hunt for and correct the false attributions people are already making. Ask employees why they think performance improved; if they credit a personality, a program, or luck instead of the new approach, restate the real cause deliberately and often.
4. 4Reshape promotion and succession criteria to require the new approach. Rewrite what gets someone advanced so that the next generation of managers personifies the new behaviors, not the old ones.
5. 5Bring the board of directors into the transformation in enough detail that they can vet succession at the top. If the board doesn't understand the change, it cannot see when a candidate is not a change leader.
6. 6Hold the line long enough — three to ten years for a whole company — before treating the new approaches as safe. Until then, treat them as fragile and subject to regression the moment change-effort pressure is removed.

In Coleen's department, a 'customer first' strategy drove real performance improvements while she was head. But because the gains happened during the tenure of a charismatic, flamboyant leader, and no one made the causal link explicit, employees connected the improvement to her personal style rather than to the strategy. The lesson that actually embedded itself into the culture was 'Value Extroverted Managers' instead of 'Love Thy Customer.' The correct behavior was never anchored — the wrong one was. Contrast this with the failed successions Kotter watched, where retiring CEOs were the change champions but their successors, though not resisters, were not change leaders either; because the boards did not understand the transformations in detail, they could not see the problem and one bad succession decision at the top undid years of work.

• If new behaviors have not yet produced visible results, then do not attempt cultural anchoring yet — you have nothing credible to point to.
• If employees are crediting a personality, a program, or luck for improvements, then intervene immediately and restate the real cause, because a false link will embed the wrong lesson.
• If promotion criteria still reward the old behaviors, then reshape them before celebrating — otherwise the transformation rarely lasts.
• If the board is not an integral part of the change effort, then treat top-level succession as an unmanaged risk, because one bad choice can undermine a decade of work.
• If the first major improvement tempts you to declare victory, then stop — changes take three to ten years to sink into the culture and remain fragile until then.

• Declaring victory too soon: paying and thanking consultants at the first completed project. Tell — celebration language ('the job is mostly done') appears before any evidence the original goals were met or that employees accept the new approach.
• Leaving people to make their own connections: performance improves but no one names the cause. Tell — employees attribute gains to a leader's charisma or a program instead of the new strategy.
• Not reshaping promotion criteria: the change effort ran, but advancement rules stayed unchanged. Tell — the next generation of managers still embodies old behaviors.
• One bad succession at the top: a retiring champion is replaced by someone who is not a resister but not a change leader either. Tell — a board that cannot describe the transformation in detail rubber-stamps the successor.
• Removing pressure before roots are set: assuming a few years is enough. Tell — 'weary troops let themselves be convinced they won,' change halts, and irrelevant traditions creep back.

• ▸Demonstrated result: name one measured performance improvement this effort produced.
• ▸Causal behavior: state the specific behavior/attitude that produced that result.
• ▸Current attribution: what do employees actually believe caused the improvement?
• ▸Correction message: the exact restatement you will repeat to fix a false link.
• ▸Promotion criteria change: what rule was rewritten to require the new approach.
• ▸Succession candidates: who is next at the top, and do they personify the new behavior (Y/N)?
• ▸Board involvement: can the board describe this transformation in detail (Y/N)?
• ▸Time elapsed vs. 3–10 year window: how long have changes had to sink in?
• ▸Regression watch: which old traditions are most likely to creep back once pressure lifts?

1. 1Separate management from leadership before you staff the effort: management makes existing systems work; leadership builds or transforms systems and takes you into unknown territory. Assign leadership tasks—defining direction, aligning people, inspiring them—to a named set of people, not to management processes.
2. 2Assemble a guiding coalition of the president/GM/department head plus another five, fifteen, or fifty people, selecting for four assets: formal position power, information and expertise, reputations and relationships, and capacity for leadership. Do not settle for a weak committee or a single charismatic individual.
3. 3Insist on strong line leadership inside the coalition. If it is led only by a staff head from HR, quality, or strategic planning, expect it to lack the power to overcome inertia—recruit key line managers.
4. 4Build trust across the coalition through carefully planned off-site events, lots of talk, and joint activities, then develop a common goal that is sensible to the head and appealing to the heart so members transcend short-term parochial interests.
5. 5Distribute leadership downward: let middle and lower-level people create conditions for change (raise urgency, confront top management with data) rather than waiting for the top. Give them cover to attack complacency without being labeled poor team players.
6. 6Treat leadership as a lifelong learning discipline, not a fixed trait—since the speed of change keeps increasing, keep building the skill so it grows as fast as the challenges do.

A middle manager in a large travel-related services company almost single-handedly created the conditions for transformation despite having no top-level authority. Using a nonroutine assignment—putting a product through a new distribution channel—as an excuse, she hired consultants who concluded the firm could not use the channel until it fixed a half-dozen fundamental problems. Her peers ran for cover, but she plunged ahead, using political savvy to deflect the denial and anger onto the consultants with lines like, "Did the consultants screw up or is there something important here?" and "You believe this? So do Gerry and Alice. Have the three of you ever talked about these issues?" This is leadership—defining direction and aligning people—exercised from below, not from a formal management post. Kotter notes that even in the worst organizations, 20 to 30 percent of senior people know the enterprise isn't living up to its potential and want to act; her initiative gave them the opening. It works only because some top-level appetite for change exists; a brave revolutionary below always fails if all of senior management is committed to the status quo.

• If a task means building or transforming a system into unknown territory, then it needs leadership; if it means making a known system work, then it needs management—staff accordingly.
• If your guiding coalition is a single executive or a weak committee, then expect countervailing forces (tradition, short-term self-interest) to win—add people with position power, expertise, relationships, and leadership capacity.
• If the coalition is led by a staff head without strong line leadership, then it will not achieve the required power—recruit a key line manager.
• If you are in middle management, urgency is needed, and senior leadership will not provide it and cannot be moved, then a smart career decision may be to move elsewhere.
• If everyone in senior management is a cautious status-quo manager, then a brave revolutionary below will fail—verify the 20-30 percent who want change exists before pushing.

• Relying on a purely managerial mindset to drive transformation—the tell: high-quality people and detailed plans, yet change stalls because no one is defining direction, aligning, or inspiring.
• Assuming leadership must come only from top management—the tell: initiatives wait on the CEO while capable middle-level people who could create conditions for change sit blocked.
• Confusing an active supporter at the top with a coalition—the tell: the head endorses change but no five-to-fifty-person team pulls together, so inertia quietly reasserts itself.
• Letting a staff executive substitute for line leadership—the tell: an HR, quality, or strategic-planning head runs the effort and it never gains power against massive inertia.
• Treating leadership as a fixed personal trait rather than something developed through lifelong learning—the tell: skills plateau while the speed of change and the challenges keep outgrowing them.

• ▸Change task & type: name it, then mark leadership (build/transform) or management (make work)
• ▸Position power: who holds formal authority so laggards can't easily block progress
• ▸Expertise & information: who supplies the relevant knowledge for sound decisions
• ▸Reputations & relationships: who carries credibility and networks across the org
• ▸Leadership capacity: who can define direction, align, and inspire (not just administer)
• ▸Line leadership present?: name the key line manager anchoring the coalition
• ▸Trust-building plan: off-site events and joint activities scheduled to build trust
• ▸Common goal: state it so it is sensible to the head and appealing to the heart
• ▸Distributed leadership: name middle/lower-level people empowered to raise urgency

1. 1Sequence the eight stages in order; do not skip. Establish urgency, build a guiding coalition, develop vision and strategy, communicate the vision, empower broad-based action, generate short-term wins, consolidate gains, then anchor new approaches in culture.
2. 2Attack complacency first and hardest. Name the specific external threats and opportunities (globalization, competitor countermoves, weak feedback) so people stop saying 'our problems aren't that terrible' or 'they're all over there.' Raise urgency without raising anxiety.
3. 3Assemble a guiding coalition with real power: the top line manager plus five, fifteen, or fifty people carrying formal titles, information and expertise, reputations and relationships, and leadership capacity. Include line leadership, not just staff heads from HR, quality, or planning.
4. 4Write a sensible vision that directs, aligns, and inspires so employees can make decisions without interminable debate. Do not let plans and programs play the role of vision.
5. 5Empower broad-based action by removing obstacles the coalition can identify as blocking implementation, then program in short-term wins early to sustain morale during the long middle.
6. 6Consolidate each win to produce more change rather than declaring victory; use credibility from wins to tackle bigger systems. Only at the end anchor new approaches in the culture so countervailing forces cannot reverse them.

Adrien, head of a specialty chemicals division, saw globalization creating clear threats and opportunities but skipped urgency-building, assuming others could be induced, pushed, or replaced. He launched a dozen initiatives day and night; within two years each sank in a sea of complacency. His new product strategy took so long that competitor countermoves erased the benefit, his reengineering project failed to secure funding, and a reorganization was talked to death by skilled filibusterers. Frustrated, he acquired a smaller firm already doing what he wanted—yet his low-urgency people ignored the acquisition's lessons and actively stifled the new unit's ability to keep performing. The transformation failed because he never established a high enough sense of urgency and never built a powerful guiding coalition; individual competence and threats could not overcome tradition and inertia. Durable transformation would have required lowering complacency first, then pulling a powerful team together before ordering initiatives forward.

• If complacency levels are high, then stop launching initiatives—transformations always fail to achieve objectives under high complacency; lower it first.
• If you are relying on a single competent or charismatic executive or a weak committee, then expect countervailing forces to win; build a coalition powerful in titles, expertise, relationships, and leadership.
• If the guiding coalition has no strong line leadership (led only by a staff head from HR, quality, or planning), then it will never gain the power to overcome inertia—recruit key line managers.
• If small decisions generate interminable debate and heated conflict, then your vision is missing or unsound—clarify it before proceeding.
• If you feel impatient ('enough with preliminaries'), then direct that impatience into team-building and vision work, not into ordering two people to finish the job.

• Allowing too much complacency: the tell is initiatives sinking despite inducements and threats, and people saying 'I'm doing my job just fine.'
• Confusing urgency with anxiety: the tell is people becoming defensive, retreating deeper into foxholes, and morale slipping instead of energy rising.
• Building a weak or staff-led coalition: the tell is apparent early progress—structure changed, reengineering launched—that later gets undermined by passive resistance and a task force that limps along eighteen months then fades.
• Underestimating vision: the tell is a list of confusing, incompatible, time-consuming projects, with plans and programs trying to play the role of vision.
• Declaring victory too early / not anchoring in culture: the tell is new approaches reversing once attention moves on, because the culture never absorbed them.

• ▸Urgency level (rate high/medium/low and cite the specific external threat driving it)
• ▸Complacency sources present (list: past success, no visible crisis, low standards, weak feedback)
• ▸Guiding coalition members (names + title, expertise, relationships, leadership they bring)
• ▸Line leadership confirmed (yes/no — is a key line manager, not a staff head, leading?)
• ▸Vision statement (one sentence that directs, aligns, and inspires)
• ▸Vision test (name a recent decision the vision resolved without interminable debate)
• ▸Obstacles to broad-based action (list blockers the coalition must remove)
• ▸Short-term wins scheduled (specific, dated, visible wins to sustain morale)
• ▸Anchoring plan (how each new approach becomes 'the way we do things here')

1. 1Confront complacency honestly: name the sources feeding it—too much past success, absence of visible crises, low performance standards, weak external feedback—so you can attack the specific causes rather than the symptom.
2. 2Gather and expose real external data. Give managers unfiltered facts about competitors, customers, and margins (as in the specialty chemicals and week-long retreat cases) so the status quo becomes visibly indefensible.
3. 3Separate urgency from anxiety. Do not drive up fear; that pushes people 'deeper into their foxholes.' Frame problems and opportunities so people feel the need to act, not the need to defend.
4. 4Audit your own behavior for signals that reinforce the status quo—celebrating adequacy, tolerating filibustering, protecting comfort zones—and stop sending them.
5. 5Refuse to plunge into initiatives before urgency is high enough. Resist the 'enough with the preliminaries' impulse; low urgency guarantees the transformation fails to reach its objectives.
6. 6Build urgency broadly among fellow managers and employees, not just in your own head—Adrien's failure was that few others saw the dangers as clearly as he did, and inducements and threats did not close that gap.

Adrien, newly named head of a large corporation's specialty chemicals division, saw clearly the problems and opportunities created by globalization. He worked day and night launching a dozen initiatives, but recognized few others shared his view—he assumed they could be induced, pushed, or replaced. Because he never raised urgency in his people, complacency swallowed his efforts: his product strategy took so long to implement that competitors' countermoves erased any benefit, he couldn't secure funding for reengineering, and a reorganization was 'talked to death by skilled filibusterers.' In frustration he acquired a smaller firm already executing his ideas—then watched his low-urgency people ignore the acquisition's lessons and actively stifle the very capabilities that had made it successful. Two years of effort produced sinking initiatives and a wrecked acquisition. The lesson: force and inducement cannot substitute for a shared perception that the status quo is unacceptable.

• If you find yourself thinking 'they can be induced, pushed, or replaced,' then stop—you are substituting force for urgency and Adrien's outcome is likely.
• If morale or short-term results dip when you reduce complacency, then hold course rather than retreat; being paralyzed by downside possibilities is a known failure mode.
• If people are becoming defensive and burrowing in, then you have created anxiety, not urgency—reframe around opportunity and honest data instead of threat.
• If fewer than most of your key managers and employees agree the status quo is unacceptable, then urgency is too low to launch initiatives—do not proceed.
• If your organization shows no visible crisis, high past success, and weak external feedback, then assume complacency is high by default and treat raising urgency as your first job.

• Overestimating how much you can force change; the tell is reliance on inducements and threats while initiatives quietly stall.
• Confusing urgency with anxiety; the tell is rising defensiveness and resistance rather than movement.
• Impatience—'enough with the preliminaries, let's get on with it'; the tell is skipping the urgency-building phase to jump to action.
• Inadvertently reinforcing the status quo through your own actions; the tell is that you can't see why nothing moves despite your effort.
• Believing your own clear perception is enough; the tell is that you see the dangers but almost no one else in the organization does.

• ▸Complacency sources present: check which apply—past success, no visible crisis, low standards, weak external feedback.
• ▸External evidence assembled: list the competitor/customer/margin data you will put in front of managers.
• ▸Urgency vs. anxiety check: state how each message frames a problem or opportunity, not a threat.
• ▸Self-reinforcement scan: name your own behaviors that signal the status quo is acceptable.
• ▸Breadth of urgency: estimate the share of key managers/employees who agree the status quo is unacceptable.
• ▸Force-substitution flag: note any place you are relying on inducement, threat, or acquisition instead of shared urgency.
• ▸Downside tolerance: pre-commit to what morale/result dips you will absorb without retreating.
• ▸Go/no-go gate: state the urgency threshold you require before launching initiatives.

1. 1Start with the head of the unit — president, division general manager, or department head — but do not stop there; recruit another five, fifteen, or fifty people who will pull together as a team committed to improved performance.
2. 2Audit the coalition against four asset classes: formal titles (position power), information and expertise, reputations and relationships (credibility), and demonstrated capacity for leadership. A gap in any one leaves you vulnerable to countervailing forces.
3. 3Include the key line managers, not just staff heads. Never assign the effort to a staff executive from human resources, quality, or strategic planning as the leader — no matter how capable they are, staff-led coalitions never reach the required power.
4. 4Accept that some of the most senior people won't buy in at first; build the coalition without them rather than waiting. The group rarely includes all top people.
5. 5Bind the group with trust and a shared goal so it acts as a team, not a committee where most work falls to a small dedicated subgroup while others stay disengaged.
6. 6Establish a high enough sense of urgency first (chapter 3) — a coalition assembled amid complacency will be talked to death by skilled filibusterers.
7. 7Give the coalition real authority to drive the effort, not the diluted mandate of a task force, work-stream, or project management office, which can help but lack sufficient power for the hardest tasks.

An executive is handed responsibility for a 'quality improvement' task force, and the next two years become the least satisfying of her career. The task force does not include even one of the three key line managers in the firm. She struggles to schedule the first meeting because members complain of being exceptionally busy — the first tell of trouble. The group becomes a caricature of a bad committee: slow, political, aggravating, with most work done by a small dedicated subgroup while other members and the line managers develop little interest or understanding. Next to none of the recommendations is implemented; the task force limps along eighteen months and fades into oblivion. The failure traces to underestimating the difficulty of producing change and thus the importance of a strong coalition with line leadership — a staff-anchored group could never generate the power to overcome the firm's inertia.

• If the coalition lacks a key line manager, then stop and recruit one before proceeding — staff leadership alone never achieves required power.
• If a senior person won't buy in, then build without them rather than delaying; a full roster of the reluctant is weaker than a committed partial one.
• If you're relying on a single competent or charismatic individual, then assume tradition and inertia will win the behind-the-scenes struggle — except in very small organizations.
• If members repeatedly claim they're too busy to meet, then read it as low urgency and low commitment, not a scheduling problem — fix urgency first.
• If the vehicle is a task force, work-stream, or PMO expected to drive the whole change, then treat it as insufficient power and escalate to a real coalition.

• Assigning leadership to a staff head from HR, quality, or strategic planning; the tell is that no key line manager owns it and recommendations don't get implemented.
• Assembling a weak committee instead of a bound team; the tell is most work done by a small subgroup while others stay uninterested and uninformed.
• Relying on one executive's competence or charisma to overcome inertia; the tell is apparent early progress (structure changed, effort launched) that later gets undermined by countervailing forces.
• Building the coalition before establishing urgency; the tell is filibustering, talked-to-death reorganizations, and members too 'busy' to engage.
• Undervaluing the need for a strong team because the firm has little history of transformation or teamwork; the tell is treating the coalition as a formality rather than a power base.

• ▸Senior sponsor: name the president/GM/department head actively pulling as a team member
• ▸Key line managers included: list them — flag if fewer than the firm's actual key line roles
• ▸Position power: do titles collectively command the units affected? (yes/gap)
• ▸Expertise/information: whose knowledge covers the change domain? (list + gaps)
• ▸Credibility: whose reputations and relationships buy trust across the org? (list + gaps)
• ▸Leadership capacity: who can take the group into new, unknown territory (not just manage)? (list)
• ▸Reluctant senior holdouts: name them and note the plan to proceed without them
• ▸Binding mechanism: what shared goal and trust-building holds the team together?
• ▸Urgency check: is complacency low enough for this group to act? (yes/fix first)

1. 1Establish a real sense of urgency and a powerful guiding coalition first — vision without them fails; do not draft the vision before a coalition with formal titles, expertise, reputations, relationships, and line leadership is pulling together as a team.
2. 2Draft a picture of the future that meets six tests: imaginable, desirable, feasible, focused, flexible, and communicable. Reject any draft that misses one.
3. 3Test communicability against the five-minute rule: if you cannot describe the vision in five minutes or less and get a reaction that signifies both understanding and interest, rewrite it.
4. 4Strip out operational detail. If the direction hides inside acquisition plans, marketing tactics, hiring, and office closures, extract the few basic elements of sound direction and cut everything else.
5. 5Attach strategies to the vision so it directs, aligns, and inspires action — otherwise the effort dissolves into confusing, incompatible, time-consuming projects that go nowhere.
6. 6Check that the vision makes disparate initiatives (a reengineering project, a 360-degree appraisal, a quality program, a culture effort) add up meaningfully rather than competing for energy.
7. 7Never bury the vision in exhaustive documentation. Four-inch notebooks of procedures, goals, methods, and deadlines confuse and alienate; a clear compelling statement of where it all leads rallies people.
8. 8Once set, undercommunicate by nothing — plan to over-communicate the vision, because without credible communication and a lot of it, hearts and minds are never captured and people won't make short-term sacrifices.

An executive spent much time and money producing four-inch-thick notebooks describing his change effort in mind-numbing detail — procedures, goals, methods, and deadlines — but nowhere stated clearly and compellingly where all this was leading. When he handed out hundreds of the notebooks, most employees reacted with confusion or alienation; the books neither rallied them nor inspired change, and may have had the opposite effect. Contrast this with a midsize British manufacturer's executive who, asked to describe his vision, gave a barely comprehensible thirty-minute lecture spanning acquisitions, a new marketing strategy, his 'customer first' definition, a senior hire, and closing the Dallas office. The basic elements of a sound direction were present but buried deeply. Both cases fail the same test: no focused, communicable picture of the future survives the detail. The fix in each is to extract those buried elements and state them so they pass the five-minute rule.

• If you cannot describe the vision in five minutes or less and get understanding plus interest, then you are in for trouble — stop and rewrite.
• If employees face endless debate over small decisions, then your vision is absent or too blurry to guide decision making.
• If the vision is a thirty-minute lecture or a four-inch notebook, then it is too complicated to be useful — extract the few basic elements and cut the rest.
• If separate initiatives don't add up in a meaningful way or don't stir the energy to implement them, then the vision is missing or unsound.
• If urgency is low or the guiding coalition lacks line leadership, then do not proceed to vision — necessary preconditions are unmet.

• Underestimating the power of vision — sensing difficulty, people manipulate events quietly behind the scenes and avoid public discussion of direction; the tell is heated conflict over insignificant tactical choices that saps energy and morale.
• Producing direction that is too complicated or blurry — the tell is a thirty-minute answer to 'what is your vision?' with the real direction buried inside tactics.
• Drowning the vision in documentation — the tell is hundreds of detailed notebooks that produce confusion or alienation instead of rallying people.
• Skipping the preconditions — treating vision as sufficient when urgency and a strong guiding coalition are the necessary base; the tell is initiatives sinking 'in a sea of complacency' despite a stated direction.
• Undercommunicating by a factor of 10 or more — developing a good vision then selling it with a few meetings or memos; the tell is employees who never make the short-term sacrifices because their hearts and minds were never captured.

• ▸One-sentence future picture: state where this change leads in a single line.
• ▸Imaginable check: describe what the future looks like concretely.
• ▸Desirable check: name the benefit that makes people want it.
• ▸Feasible check: note why it is realistic and achievable.
• ▸Focused/Flexible check: confirm it is clear enough to guide yet allows individual initiative.
• ▸Attached strategies: list the strategies that move the organization toward this vision.
• ▸Five-minute delivery: can you say all the above in under five minutes? (Y/N).
• ▸Reaction test: record whether a real listener showed both understanding and interest.
• ▸Buried-detail cut: list operational specifics (acquisitions, hires, closures, procedures) removed to keep it clear.

1. 1Simplify the vision until you can describe it in five minutes or less and get a reaction signaling both understanding and interest — eliminate jargon, buzzwords, and thick-notebook detail.
2. 2Estimate your total yearly intracompany communication (all meetings, memos, newsletters, speeches), then plan to route a large fraction of it to the vision — assume your first instinct undercommunicates by a factor of 10, 100, or even 1,000.
3. 3Deploy across multiple channels, not one: speeches, meetings, newsletters, memos, informal conversations — do not rely on a few meetings or a few memos.
4. 4Enlist every manager, not just the CEO. One head making speeches while managers stay silent still leaves volume woefully inadequate; the guiding coalition must all send the message.
5. 5Make communication two-way: describe the vision and read the reaction, so debate can be settled by the vision rather than dissolving into interminable argument over small decisions.
6. 6Audit your own deeds against your words before every visible decision — promotions, funding choices, closures — because behavior inconsistent with the message is the most powerful (and most destructive) form of communication.
7. 7Repeat continually; treat the message as under-heard until managers, asked cold, can restate it in their own words, not as 'a bunch of jaw movements.'

One of the finest CEOs Kotter knows failed at this in the early 1980s. At the time, it seemed like his team was spending a great deal of effort trying to communicate their ideas. But a few years later they could see the distance they went fell short by miles. Worse, they would occasionally make decisions others saw as inconsistent with their communication — enough that he suspects some employees thought they were 'a bunch of hypocritical jerks.' Contrast Conrad, the quality czar who produced four-inch-thick notebooks spelling out procedures, goals, methods, and deadlines but no clear statement of where it all led; handing out hundreds of them produced confusion and alienation rather than rallying anyone. The lesson from both: volume of paper is not communication, and words are undone by inconsistent deeds.

• If you cannot describe the vision in five minutes or less and get understanding plus interest, stop and simplify before communicating further.
• If you've used only a few meetings or memos, assume you've undercommunicated by at least a factor of 10 and multiply the channels.
• If the CEO speaks but managers are silent, treat the message as not yet delivered — recruit the managers first.
• If a visible decision (a promotion, a funding cut, a closure) contradicts the vision, expect cynicism to rise and belief to fall; fix the deed or don't make it.
• If people can't restate the vision in their own words when asked cold, the volume is still inadequate — keep repeating.

• Selling a good vision through only a few meetings or memos, then reacting with astonishment that no one understands. Tell: 'Something about customers and partnerships, wasn't it?'
• CEO does all the talking while managers stay quiet — volume looks better but is still miles short. Tell: employees heard the speech but nothing reinforces it day to day.
• Heavy newsletters and speeches undercut by highly visible individuals behaving against the vision. Tell: cynicism rises, belief drops — 'they promoted some jerk whose approach is totally inconsistent.'
• Substituting thick programs and plans for vision — four-inch notebooks of procedures and deadlines. Tell: recipients react with confusion or alienation, not energy.
• Communicating often but in dense jargon ('boundaryless organization and a paradigm shift strategy'). Tell: interesting ideas are buried and the statement works very poorly no matter how often repeated.

• ▸Five-minute vision statement: write it plainly; if it can't be said in five minutes, cut it
• ▸Understanding/interest test result: note the reaction you got from a real listener
• ▸Channels in use: list every channel (speeches, meetings, memos, newsletters, informal talks)
• ▸Total yearly communication estimate: rough count of all internal messaging
• ▸Vision's share of that volume: what fraction currently carries the vision — aim far higher
• ▸Manager participation: name managers actively sending the message vs. those silent
• ▸Two-way feedback loop: how you're capturing and answering employee reactions
• ▸Deed-word consistency check: list upcoming visible decisions and flag any that contradict the message
• ▸Cold-recall check: can a random employee restate the vision? yes/no + what they said

1. 1Confirm the prerequisites exist first: broad-based empowerment is stage five and depends on stages one through four. If people have not accepted the vision (stage four), they will neither use their empowerment nor put in the effort — rework the vision before touching structures.
2. 2Attack structural barriers: identify formal structures that make employees responsible for results but powerless to act on the vision, and change the reporting lines, boundaries, or role definitions that box them in.
3. 3Attack the skill barrier: audit whether employees actually have the training the new vision demands; most disempowerment here is 'lack of training,' so fund and schedule real skill-building rather than assuming existing competence transfers.
4. 4Attack the systems barrier: find information and personnel systems (measurement, appraisal, compensation) that reward the old behavior and contradict the vision, and rewire them so acting on the vision is systemically supported, not punished.
5. 5Confront disempowering supervisors: locate managers — often in the missing middle — who block subordinates who want to help, and require them to change behavior or move them out, since a lack of leadership in middle management stalls otherwise-addressed change.
6. 6Recheck alignment with the top: verify corporate headquarters and the CEO are not sending messages employees read as inconsistent with the new direction, because inconsistent signals from above sabotage empowerment efforts even when local work is done well.

In one multidivision case, twelve division officers rated their change work as roughly 40 percent complete on vision-communication and only about 10 percent on empowerment, and their eighteen months of good progress was slowing into frustration. Probing the cause, they kept returning to 'corporate headquarters': the CEO and key corporate individuals were not truly part of the guiding coalition, so higher-order principles were never decided. That gap meant messages from corporate reached employees as inconsistent with the new direction, and those mixed signals directly sabotaged the empowerment efforts below. Because the vision stayed fuzzy, the division could not even target credible short-term wins. The lesson is operational: their empowerment did not fail on the front line — it failed because an upstream barrier (misaligned top leadership and an unclear vision) was left standing, and empowerment cannot survive that.

• If people have not genuinely accepted the vision, then stop and reformulate it before removing barriers — empowerment built on a rejected or poorly formulated vision only wastes time and resources.
• If employees are held responsible for results but lack authority, training, or supportive systems, then the fault is structural/systemic, not personal — fix the barrier, not the person.
• If corporate or the CEO sends signals employees read as inconsistent with the vision, then treat that misalignment as the priority barrier, because it will sabotage every downstream empowerment effort.
• If a supervisor consistently blocks subordinates who want to act on the vision, then require behavior change or remove them — leaving a disempowering manager in place cancels the empowerment of everyone under them.
• If progress was strong for 12-18 months and is now stalling, then look upstream for an unaddressed earlier-stage barrier rather than pushing harder at the front line.

• Skipping straight to empowerment before the vision is accepted — the tell: you announce authority and autonomy but employees don't take advantage of it or put in effort to secure wins.
• Blaming individual employees for inaction when structure, systems, training, or supervisors are the true obstacle — the tell: 'our people just resist change' while the appraisal and pay systems still reward old behavior.
• Ignoring the missing middle — the tell: a manager who wants change but finds most of the management team quietly blocking it, with subordinates who want to help being held back.
• Leaving top-level messages inconsistent with the vision — the tell: employees interpret corporate communications as contradicting the new direction, and empowerment efforts get sabotaged despite local effort.
• Treating empowerment as a one-time authorization event rather than the sustained removal of four distinct barriers — the tell: you 'empowered' the team once but the disempowering systems and supervisors are still in place.

• ▸Vision acceptance check: evidence that target employees understand and accept the vision (yes/no + proof).
• ▸Structural barrier: which reporting line, boundary, or role definition boxes employees in against the vision.
• ▸Skill barrier: which specific training the vision demands but employees currently lack.
• ▸Systems barrier: which measurement, appraisal, or compensation system rewards old behavior over the vision.
• ▸Supervisory barrier: name the manager(s) blocking subordinates who want to act, and the required behavior change.
• ▸Top-alignment check: any corporate/CEO messages employees read as inconsistent with the new direction.
• ▸Removal owner + date: who fixes each barrier and by when.
• ▸Empowerment evidence: observable action by employees on the vision that confirms the barrier is actually gone.