How do I apply the idea that schema evolution in organizations?

The most direct way to practice is through a focused exercise: Identify one organizational schema that has been stable for more than five years. Ask: (1) What environmental conditions was this schema adapted to when it formed? (2) Have those conditions changed? (3) If the conditions have changed, has the schema been updated to reflect the new conditions? (4) If the schema has not been updated, what information is the schema filtering out that might signal the need for change? Write a one-paragraph description of what the updated schema might look like — the mental model the organization would hold if it were adapting to current conditions from scratch rather than continuing a historical schema.

Common pitfall: Two failures that are mirror images. The first is schema rigidity — refusing to update schemas until a crisis forces the change. This produces organizations that are perfectly adapted to the past and catastrophically maladapted to the present, which is the pattern described in the example above. The second is schema volatility — updating schemas so frequently that the organization never develops the deep competence that comes from sustained schema commitment. An organization that changes its strategy schema every quarter, its process schemas every month, and its values schemas with every new leadership hire never develops the operational depth that stable schemas provide. The discipline is to distinguish between schemas that need to evolve (because the environment has changed) and schemas that need to persist (because they represent hard-won wisdom that remains valid).

This practice connects to Phase 82 (Organizational Schemas) — building it as a repeatable habit compounds over time.