Core Primitive
Systemic change requires allies at multiple levels of the organization. No individual — regardless of position or authority — can change a system alone, because systems are maintained by the collective behavior of everyone who operates within them. A coalition for change is a group of people across organizational levels and functions who share a commitment to the change and are willing to invest their influence, expertise, and effort in making it happen. Building this coalition is not a political tactic — it is a structural necessity, because the change must be supported by people in the positions where the system is actually operated.
Why coalitions, not mandates
The most common misconception about organizational change is that it can be mandated from above. A CEO who announces a new strategy, a VP who implements a new process, a director who introduces a new tool — each believes that authority plus communication equals change. It does not.
Authority can mandate compliance. It cannot mandate commitment. And systemic change requires commitment — the active, sustained investment of energy and attention from people across the organization who must change their daily behavior for the new system to work. Compliance produces the appearance of change while the underlying behavior remains unchanged. Commitment produces genuine behavioral shift because the people involved believe the change serves their interests and is worth their effort.
John Kotter's research on organizational transformation found that the most common cause of change failure is the absence of a powerful guiding coalition — a group of people with enough position power, expertise, credibility, and leadership to drive the change effort. Without this coalition, change efforts get blocked by the first serious resistance, stalled by the first resource constraint, or abandoned at the first leadership transition (Kotter, 1996).
The anatomy of an effective coalition
An effective change coalition has three properties that distinguish it from a committee, a task force, or an advocacy group.
Organizational diversity
The coalition must span the system it is trying to change. A coalition of engineers cannot change the product development system because the system includes product management, design, sales, customer success, and leadership — all of whom must change their behavior for the system to change. A coalition of middle managers cannot change the incentive system because the incentive system is designed and maintained by senior leadership and HR.
The diversity requirement extends to perspective as well as position. The coalition should include skeptics as well as enthusiasts — people who see the risks and limitations of the proposed change as well as its benefits. A coalition of pure enthusiasts will design a change that ignores legitimate concerns, producing unnecessary resistance and avoidable failures.
Resource commitment
Coalition membership requires more than agreement — it requires commitment of time, attention, and political capital. Members must be willing to invest their personal credibility in the change, to spend time on change activities that compete with their regular responsibilities, and to advocate for the change in contexts where advocacy carries political risk.
The resource commitment distinguishes a coalition from a mailing list. Many organizational change efforts create large "steering committees" or "advisory boards" whose members attend quarterly meetings but invest no personal resources between meetings. These bodies provide the appearance of broad support without the reality of committed action.
Decision authority
The coalition must include members with the authority to make the decisions the change requires — budget allocation, incentive modification, process redesign, personnel changes. Without decision authority, the coalition can analyze, recommend, and advocate — but it cannot act. And systemic change requires action: structural changes, resource reallocations, and incentive modifications that only authorized decision-makers can implement.
Building the coalition
Coalition building follows a sequence that reflects the practical realities of organizational life: start with trust, expand through evidence, and consolidate through shared success.
Phase 1: The nucleus (1-3 people)
Every coalition starts with a small nucleus — two or three people who share a diagnosis of the problem and a vision of the solution. The nucleus is formed through personal relationships and direct conversation, not through organizational mechanisms. The nucleus members trust each other, complement each other's capabilities, and are willing to invest personal credibility before the change effort has organizational legitimacy.
The nucleus performs the initial system analysis (Identify the system before trying to change it), identifies the leverage points (Leverage points in systems), and designs the preliminary change approach. This work is pre-organizational — it happens before any formal change initiative is launched, because launching a formal initiative without a clear analysis and a committed nucleus produces a change effort that is visible but powerless.
Phase 2: The evidence base (2-6 months)
The nucleus grows by demonstrating that the proposed change is viable. This demonstration takes one of three forms: a pilot program (Pilot programs as system experiments) that shows the change working in a bounded context, an analysis that quantifies the cost of the current system, or an external example that shows a comparable organization succeeding with the proposed change.
Evidence is the currency of coalition expansion. Each person who joins the coalition does so because the evidence convinces them that the change is worth their investment. Without evidence, coalition expansion depends on personal persuasion — which is slower, less scalable, and less durable than evidence-based recruitment.
Phase 3: The critical mass (6-18 months)
The coalition reaches critical mass when it includes enough organizational influence to overcome the resistance mapped in The system resists change and Stakeholder mapping for systemic change. Critical mass is not a majority — it is a concentration of influence at the key decision points and operational nodes where the system must change.
Everett Rogers' diffusion of innovations research identified the "critical mass" threshold as the point at which enough adopters exist that the innovation's continued adoption becomes self-sustaining. In organizational change, the critical mass threshold is reached when enough influential people are committed to the change that their collective behavior creates a new social norm — making the change the expected behavior rather than the exceptional behavior (Rogers, 2003).
Phase 4: The formal launch
Only after the coalition has reached critical mass should the change be formally launched. The formal launch — the announcement, the resource allocation, the timeline — succeeds because the coalition has already done the preparatory work: the system has been analyzed, the leverage points identified, the evidence generated, the stakeholders mapped, and the political support assembled. The formal launch is the visible culmination of months of invisible coalition work.
Coalition maintenance
Building the coalition is the beginning, not the end. Coalitions require ongoing maintenance to sustain their effectiveness through the long arc of systemic change.
Shared wins. The coalition must celebrate incremental successes — visible evidence that the change is working. Shared wins reinforce the coalition members' commitment, provide evidence for recruiting additional members, and counter the narrative of resistance that the change is failing.
Conflict resolution. Coalition members will disagree on implementation details, priorities, and pace. These disagreements are healthy — they produce better decisions — but only if they are resolved constructively. Unresolved conflicts fragment the coalition, creating factions that undermine the change effort.
Adaptation. The change plan will need to be modified as implementation reveals realities that were not visible during planning. The coalition must be willing to adapt — adjusting the approach based on evidence without abandoning the direction. Rigid adherence to the original plan in the face of contrary evidence erodes the coalition's credibility and effectiveness.
The Third Brain
Your AI system can help you design and manage coalition-building strategies. Describe the change you are pursuing, the organizational context, and the coalition members you have recruited so far, and ask: "Assess the current coalition's organizational coverage: which parts of the system are represented, and which are missing? Who are the most important potential coalition members we have not yet recruited? What evidence or arguments would be most persuasive for each? What is the coalition's current influence relative to the resistance forces — are we at critical mass, or do we need more members?"
From coalition to experiment
A coalition provides the human infrastructure for systemic change — the people, influence, and commitment needed to drive the change. But the coalition's first action should not be full-scale implementation. It should be experimentation — testing the proposed change on a small scale to generate evidence, refine the design, and build confidence.
The next lesson, Pilot programs as system experiments, examines pilot programs as system experiments — the practice of testing systemic changes in bounded contexts before committing to organization-wide deployment.
Sources:
- Kotter, J. P. (1996). Leading Change. Harvard Business Review Press.
- Rogers, E. M. (2003). Diffusion of Innovations (5th ed.). Free Press.
Frequently Asked Questions