Coalition Building
Coalition Building is the practice of assembling a cross-functional group of leaders with the credibility, authority, and energy to drive a change forward. Kotter's research identified building a 'guiding coalition' as the second of his 8 steps for a reason: no single executive can drive enterprise change alone, and changes that depend on a single sponsor die when that sponsor moves on, gets distracted, or loses political capital. A real coalition has four characteristics: (1) Position power — enough authority that others can't easily block. (2) Expertise — diverse viewpoints across functions. (3) Credibility — people the org actually respects, not just senior titles. (4) Leadership — ability to drive change, not just manage it. Most failed transformations had a 'sponsor' (one executive) but not a coalition.
The Trap
The trap is confusing executive endorsement with coalition. A CEO sending a memo and showing up at the kickoff is endorsement, not coalition. A real coalition meets weekly, shares decision-making, presents a united public face, and personally absorbs political costs. The second trap: building a coalition of people who already agree. A coalition of cheerleaders has no value — it doesn't surface real opposition or improve the design. A real coalition includes 1-2 credible skeptics whose buy-in changes minds across the org. Without them, the coalition becomes an echo chamber that misses fatal flaws until they explode at scale.
What to Do
Map the coalition before announcing the change. Identify 6-10 people who must visibly back the change for it to succeed. For each, score: (1) Their position power, (2) Credibility with affected populations, (3) Current stance on the change (supporter / neutral / opposed), (4) What they need to commit. For neutrals and opponents, run 1:1 'coalition negotiation' sessions BEFORE public announcement — surface their objections, address them, and earn their commitment to either active support or active neutrality. Then build coalition rituals: weekly 30-min sync, shared dashboard, joint communications, and a 'no surprises' rule. KnowMBA POV: most failed transformations had a list of sponsors, not a working coalition. The difference is shared accountability for outcomes.
Formula
In Practice
When Alan Mulally became Ford CEO in 2006, the company was facing $17B in losses and existential risk. Mulally's first major move was building a guiding coalition through the now-famous 'Business Plan Review' (BPR) weekly meeting. He required all top executives to attend in person every Thursday, present color-coded status (green/yellow/red), and tell the truth about their function's status. Initially executives resisted (the first weeks had no 'red' indicators, which Mulally knew was impossible — they were all hiding problems). When Mark Fields finally showed a red indicator, Mulally publicly thanked him. Within months, the BPR became a real coalition where executives shared problems, helped each other, and made cross-functional decisions in the room. Ford was the only US automaker to avoid bankruptcy in 2008-09 — directly attributable to the coalition Mulally built before the crisis hit.
Pro Tips
- 01
The coalition must include at least one credible skeptic. A coalition of pure supporters cannot pressure-test the change and will miss fatal flaws. The skeptic's role is to surface what others won't say in front of the CEO.
- 02
Coalition rituals matter more than coalition rosters. Weekly 30-minute syncs, shared decision logs, and a 'no surprises' rule build the trust that makes joint action possible. Without rituals, a coalition is just a list of names.
- 03
The most dangerous moment for a coalition is mid-change, when the easy wins are gone and the hard tradeoffs surface. This is when individual coalition members start hedging publicly. Pre-commit to a 'we present united even when we disagree privately' rule and enforce it visibly.
Myth vs Reality
Myth
“If the CEO is committed, you don't need a coalition”
Reality
CEO commitment is necessary but not sufficient. Major change touches multiple functions; the CEO can't be the sponsor of execution in every function. Without a coalition, change relies on the CEO's bandwidth, which becomes the binding constraint.
Myth
“Bigger coalitions are stronger coalitions”
Reality
Coalitions over 10-12 people lose cohesion and become coordination overhead instead of decision-making bodies. Kotter's research suggests 6-10 is the sweet spot. Beyond that, you need a tiered structure (core coalition + extended advisory).
Myth
“Coalitions form naturally when people agree on the goal”
Reality
Coalitions require deliberate construction. Even when leaders agree on the goal, they have different functional interests, political calculations, and personal capacity. A working coalition requires explicit negotiation of each member's commitment, not assumption based on shared vision.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
You're launching a major change and want to build a guiding coalition. Your VP of Sales is the most influential leader in the company but is opposed to the change. According to coalition building research, what should you do?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Optimal Coalition Composition
Enterprise transformations 500+ employeesCoalition size
6-10 members
Cross-functional representation
All affected functions + 1 skeptic
Meeting cadence
Weekly 30-60 min minimum
Coalition longevity
Duration of change + 6 months sustain
Source: Kotter, Leading Change (1996, HBR Press) / Prosci sponsor coalition research
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Ford Motor Company (Mulally's BPR)
2006-2014
Alan Mulally inherited Ford in 2006 facing $17B in losses, declining market share, and a famously siloed culture where executives concealed problems from each other and from the CEO. Mulally's signature move was the Business Plan Review (BPR) — a Thursday morning meeting requiring all top executives to attend in person, present color-coded status (green/yellow/red), and surface real problems. Initially everyone showed all green (impossible). When Mark Fields became the first to show a red on the Edge launch, Mulally publicly thanked him. Within months, the BPR became a working coalition: executives helped each other solve problems in real-time, made joint decisions, and presented unified to the rest of Ford. The coalition was the foundation of Ford's One Ford strategy, which delivered the company through the 2008-09 crisis without bankruptcy or government bailout — the only US automaker to do so.
Loss when Mulally arrived
$17B (2006)
BPR meeting cadence
Weekly, mandatory in-person
First 'red' status indicator
Mark Fields, Edge launch
Outcome
Only US automaker to avoid 2008-09 bankruptcy
The BPR coalition wasn't an org chart — it was a ritual. The weekly cadence, the color-coded honesty, and Mulally's public reinforcement created the trust that made joint decision-making possible. Coalitions are built through behavior over time, not assembled through nomination.
Hypothetical: Healthcare System EHR Coalition Failure
2023
A 4,000-employee hospital system rolled out a new EHR with what looked like a strong coalition: CMO, CIO, CFO, COO, and three department chairs. On paper, position power was 10/10. But the coalition never met as a working group — they only convened for status updates. The CFO was privately skeptical but never raised concerns; the CMO was overwhelmed and skipped most meetings. When the rollout hit predictable pain points (workflow disruption, training gaps), the coalition fragmented publicly. Each member protected their function. Within 9 months, the rollout was officially 'on track' but practically failing — adoption at 41%, physician satisfaction at all-time lows, and three department chairs had withdrawn support. The fix: a new coalition with explicit weekly working meetings, a co-chair structure (CMO + CIO), and a 'no public hedging' agreement. Within 6 months, adoption recovered to 76%.
Original coalition position power
10/10 (looked strong)
Original coalition cohesion
2/10 (never met as a group)
Adoption at coalition failure
41%
Adoption after coalition rebuild
76% in 6 months
Position power without cohesion is theatrical. The original coalition had every senior leader on it but never functioned as a coalition — they were a list. The rebuild added rituals, working sessions, and explicit unity rules. Coalitions are operating systems, not org charts.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Coalition Building into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Coalition Building into a live operating decision.
Use Coalition Building as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.