How do I apply the idea that sustaining systemic change?

The most direct way to practice is through a focused exercise: For a change your organization has implemented, assess its sustainability using four tests: (1) Incentive alignment — are people rewarded for the new behavior or the old behavior? If the incentives still support the old behavior, the change will revert when attention shifts. (2) Process embedding — is the new behavior embedded in formal processes or dependent on informal commitment? If it depends on informal commitment, it will decay as personnel changes. (3) Feedback loop presence — is there a mechanism that detects reversion and triggers correction? Without a feedback loop, reversion is invisible until it is complete. (4) Cultural integration — has the change been incorporated into the organization's stories, rituals, and artifacts? If the culture still references the old way as 'how we do things,' the new way is temporary. For each test the change fails, design the sustainability mechanism that is missing.

Common pitfall: Confusing implementation with completion. The most common failure mode is declaring victory at implementation — announcing the change is done, dissolving the change team, and moving organizational attention to the next priority. Implementation is the midpoint of change, not the endpoint. The period after implementation — when the change must be reinforced, refined, and embedded — is where most changes succeed or fail. Kotter's research found that the most common cause of change failure is declaring victory too soon: removing the support structures while the change is still fragile (Kotter, 1996).

This practice connects to Phase 84 (Systemic Change) — building it as a repeatable habit compounds over time.