Question
What goes wrong when you ignore that systemic change is how organizations evolve?
Quick Answer
Treating systemic change as a project rather than a capability. Organizations that treat systemic change as a one-time project — something you do, complete, and move on from — develop fragile adaptations. They may successfully execute one transformation, but they do not build the organizational.
The most common reason fails: Treating systemic change as a project rather than a capability. Organizations that treat systemic change as a one-time project — something you do, complete, and move on from — develop fragile adaptations. They may successfully execute one transformation, but they do not build the organizational muscle for continuous evolution. The failure becomes visible when the next environmental shift occurs and the organization must begin the change process from scratch, having retained none of the skills, structures, or cultural infrastructure from the previous transformation. The antidote is treating systemic change as a permanent organizational capability — a skill that is practiced, refined, and maintained, not a project that is launched, completed, and archived.
The fix: Conduct a systemic change readiness assessment for your organization. Evaluate your organization's capability across the ten systemic change functions covered in this phase: (1) System identification — can you map your organization's key systems, including boundaries, components, connections, and dynamics? (L-1663) (2) Leverage analysis — can you identify which elements of the system, if changed, would produce the largest effect? (L-1664) (3) Feedback design — can you design feedback loops that reinforce desired changes and correct unintended drift? (L-1665) (4) Consequence anticipation — can you systematically anticipate unintended consequences before deploying changes? (L-1666) (5) Resistance management — can you identify and work with (not against) the system's resistance to change? (L-1667) (6) Coalition building — can you assemble the political support necessary for systemic change? (L-1669) (7) Pilot execution — can you test proposed changes in bounded experiments before full deployment? (L-1670) (8) Structural redesign — can you modify the four structural levers (incentives, information flows, decision rights, processes) to produce different outcomes? (L-1672 through L-1676) (9) Sustainability embedding — can you embed changes into the system so they persist without continuous intervention? (L-1678) (10) Change leadership — can your leaders set direction, remove obstacles, and maintain commitment over years? (L-1679) Rate each capability on a 1-5 scale. Your lowest-rated capabilities are the constraints on your organization's ability to evolve.
The underlying principle is straightforward: Organizations that cannot change their systems cannot adapt to changing environments. Evolution is not a metaphor for organizational change — it is the mechanism. Biological organisms evolve by modifying the systems (genetic, developmental, behavioral) that produce their characteristics. Organizations evolve by modifying the systems (structural, cultural, operational) that produce their outcomes. The organization that has mastered systemic change — that can identify its systems, find their leverage points, redesign their structures, and sustain the changes — has acquired the meta-capability that makes all other capabilities possible: the ability to become what the environment requires.
Learn more in these lessons