Skip to content
How to ThinkIn the Age of AI

Culture evolution not revolution

~6 min read

Core Primitive

Gradual, intentional cultural evolution is more sustainable and more effective than dramatic cultural overhaul.

Revolution — the attempt to replace one culture with another in a short period — triggers the full force of cultural resistance (Cultural resistance to change), destroys functional elements along with dysfunctional ones, and produces change fatigue that makes subsequent changes harder. Evolution — the practice of continuously adapting cultural patterns through small, deliberate adjustments — works with the sedimentation dynamic (Culture is built by repeated behavior) rather than against it, preserving what works while incrementally modifying what does not.

The revolution fallacy

Cultural revolution is seductive. A new CEO arrives and declares: "We are going to transform our culture." The language of revolution — transformation, reinvention, disruption — appeals to leadership's desire for decisive action and visible impact. But cultural revolution rarely succeeds, and when it does, the costs are enormous.

John Kotter's research found that most large-scale change efforts fail — and the failures share common patterns: declaring victory too soon, not anchoring changes in the culture, and creating a sense of urgency so extreme that it produces paralysis rather than action. Revolutionary change attempts trigger these failure patterns because they ask the organization to abandon its existing cultural infrastructure before a replacement is ready — the organizational equivalent of demolishing the building while people are still living in it (Kotter, 1996).

The evolutionary alternative does not avoid change. It achieves change through a different mechanism: continuous, incremental modification of cultural patterns through deliberate behavioral adjustments, system redesigns, and narrative shifts — each small enough to be absorbed without triggering the full force of cultural resistance (Cultural resistance to change), but cumulative enough to produce meaningful cultural shift over time.

Why evolution works

Evolution works because it aligns with the sedimentation model of culture (Culture is built by repeated behavior). Culture is built by accumulated behavioral deposits. It is also modified by accumulated behavioral deposits — new behaviors, consistently practiced, gradually shift the cultural sediment. Evolution adds new layers of behavioral sediment while allowing the old layers to be gradually buried rather than violently excavated.

Evidence-based change. Evolution produces evidence at each step. A pilot demonstrates that the new cultural pattern works in practice — not in theory, not in a presentation, not in a vision statement, but in the observable behavior and measurable outcomes of a real team. This evidence is the most powerful tool for overcoming cultural resistance: it replaces the abstraction of "this could work" with the concrete reality of "this does work."

Preserved strengths. Evolution preserves the functional elements of the existing culture while modifying the dysfunctional elements. Revolution cannot distinguish between functional and dysfunctional — it replaces everything. A culture that values deep expertise (functional) alongside resistance to external feedback (dysfunctional) can evolve to preserve the expertise while developing openness to feedback. Revolution would risk destroying the expertise in the attempt to eliminate the resistance.

Reduced resistance. Small changes trigger small resistance. Large changes trigger large resistance. Evolution breaks the cultural change into increments, each of which encounters manageable resistance. By the time the cumulative change is large enough to trigger significant resistance, much of the resistance has been pre-empted by the evidence accumulated during earlier increments.

Continuous learning. Evolution includes a learning loop: each increment produces learning about what works, what does not, and what needs to be adjusted. This learning informs subsequent increments, producing a change trajectory that improves over time. Revolution does not have this learning loop — it is a single, large bet on a design that has not been tested in the organization's specific context.

The evolution methodology

Cultural evolution follows a structured methodology that combines the behavioral approach from Culture change starts with behavior change with the feedback loops from Designing cultural feedback loops.

Phase 1: Diagnose (months 1-2)

Use the cultural measurement framework from Measuring culture to assess the current cultural state. Identify the specific cultural patterns that need to evolve (not the culture as a whole, but specific behavioral patterns within it). Prioritize: which patterns have the highest cost of continuation and the highest feasibility of change?

Phase 2: Pilot (months 2-6)

Select a bounded context — a single team, project, or process — where the desired cultural pattern can be piloted. Design the behavioral architecture (Culture change starts with behavior change) for the pilot: the structural changes that will make the new behavior the default within the pilot context. Run the pilot with explicit measurement: track both the behavioral changes and the outcomes those changes produce.

Phase 3: Learn (months 4-8, overlapping with pilot)

Analyze the pilot results. What behavioral changes occurred? What outcomes changed? What resistance emerged? What unintended consequences appeared? Use the learning to refine the approach — adjusting the behavioral architecture, the structural supports, and the change narrative based on what the pilot revealed.

Phase 4: Expand (months 6-12)

Extend the evolved cultural pattern to additional contexts, incorporating the lessons from the pilot. Each expansion is itself a mini-pilot — measured, analyzed, and refined. The expansion should be paced to the organization's absorption capacity: adding new contexts only when the previous contexts have stabilized.

Phase 5: Integrate (months 9-18)

Develop a shared framework that integrates the old and new cultural patterns. The framework acknowledges that both patterns have value — the old pattern served the organization well in its context, and the new pattern serves the organization better in the current context. This integration prevents the binary thinking that cultural revolution encourages ("old culture bad, new culture good") and instead frames the evolution as growth and adaptation.

Phase 6: Sustain (ongoing)

Incorporate the evolved cultural pattern into the organization's cultural maintenance systems — the feedback loops (Designing cultural feedback loops), the rituals (Rituals and ceremonies encode culture), the stories (Stories carry culture), and the artifacts (Artifacts reflect culture) that sustain cultural patterns over time. Without this integration, the evolved pattern will decay as the organizational attention moves to other priorities.

Evolution at scale

Cultural evolution can be practiced at multiple scales simultaneously.

Individual evolution. A single leader can evolve their personal cultural contribution by deliberately modifying their behavioral patterns. A manager who begins conducting retrospectives differently — asking "What did we learn?" instead of "What went wrong?" — is practicing individual cultural evolution.

Team evolution. A team can evolve its sub-culture through shared commitment to behavioral experiments. The team agrees to try a new practice for a month, assess the results, and decide whether to continue, modify, or abandon it.

Organizational evolution. The organization can evolve its primary culture through the phased methodology described above — piloting, learning, expanding, and integrating cultural changes across the entire organization.

The most effective approach combines all three scales: individual leaders model the new behavior, teams experiment with new practices, and the organization provides the structural support for the changes to take root.

The Third Brain

Your AI system can help you design and manage cultural evolution programs. Describe the current cultural pattern you want to evolve and the desired direction, and ask: "Design a 12-month cultural evolution plan following the diagnose-pilot-learn-expand-integrate-sustain methodology. What is the ideal pilot context? What behavioral architecture should the pilot use? What measurements will indicate whether the evolution is working? What is the pacing for expansion — how quickly should additional contexts be added?"

The AI can also help you monitor evolution in progress: "We are in month six of our cultural evolution. Here is what we have observed: [pilot results, behavioral changes, resistance patterns, unintended consequences]. Is the evolution on track? What adjustments should we make for the expansion phase? What risks should we anticipate?"

From evolution to infrastructure

Cultural evolution is the practice. Cultural infrastructure is the product. When cultural evolution is practiced continuously — when the organization habitually senses its cultural health, adjusts its behavioral patterns, and integrates the changes into its operating systems — the culture becomes truly self-maintaining infrastructure.

The next and final lesson of this phase, Culture as executable infrastructure means it runs the organization, closes Culture as Infrastructure with the integrative insight: culture as executable infrastructure means it runs the organization. When the cultural infrastructure is well-designed and well-maintained, it produces aligned, adaptive behavior as an emergent property — without requiring constant intervention, enforcement, or management attention.


Sources:

  1. Kotter, J. P. (1996). Leading Change. Harvard Business Review Press.

Put it into practice

Exercise

Identify one cultural evolution you want to make — a gradual shift from a current cultural pattern to a modified one. Design a 12-month evolution plan: (1) Month 1-3: Identify one context (a single team, project, or process) where the desired cultural pattern can be piloted without disrupting the broader organization. (2) Month 3-6: Run the pilot and collect evidence. What works? What does not? What needs to be adjusted? (3) Month 6-9: Expand to a second context, incorporating lessons from the first pilot. (4) Month 9-12: Develop a shared framework that integrates the old and new cultural patterns, recognizing that both have value in appropriate contexts. The key discipline: resist the urge to accelerate. Each phase builds the evidence base, the behavioral familiarity, and the organizational readiness that the next phase requires.

More on putting it into practice

See it in action

A media company, Narrative, needed to evolve from a culture of perfectionism (every piece must be flawless before publication) to a culture of iteration (publish quickly, learn from feedback, improve continuously). The CEO's first instinct was revolution: announce the new culture, redesign the editorial process, and expect immediate behavior change. A cultural advisor convinced her to try evolution instead. Month 1: The team identified one publication channel (the blog) where iteration would be piloted. The premium publications maintained their perfectionist standards. Month 3: The blog team's faster publishing cadence produced measurable engagement improvements, creating evidence that iteration worked. Month 6: A second channel (the newsletter) adopted the iterative approach, informed by the blog team's learning. Month 9: The team developed a shared framework distinguishing 'flagship' content (where the perfectionist standard applied) from 'learning' content (where the iterative standard applied). Month 12: The distinction had evolved further — the team recognized that even flagship content benefited from iterative development, just with a higher publication threshold. By month 18, the culture had evolved substantially: the team valued iteration as a methodology while maintaining quality as a standard. The evolution preserved the genuine strength of the original culture (commitment to quality) while adding the adaptive capacity of iteration. A revolution would have destroyed the quality commitment in the attempt to install iteration — losing a strength to gain a capability.

Watch for the failure mode

Using evolution as an excuse for inaction. The distinction between evolution and revolution is not the distinction between slow change and no change. Cultural evolution requires active, deliberate, sustained effort — the same effort as revolution, but distributed over a longer timeline and directed at incremental modifications rather than wholesale replacement. The failure mode is labeling the status quo 'evolution' to avoid the discomfort of genuine cultural change. Real evolution is visible: the culture measurably shifts over time. If the culture looks the same after twelve months of 'evolution,' the evolution is not happening — it is just inaction disguised as patience.

Make it stick

This lesson synthesizes the culture change arc (Culture change is slow and difficult through Cultural resistance to change) with the cultural maintenance framework (Designing cultural feedback loops) into a practical approach: evolution. Culture change is slow and difficult established that culture change is slow. Culture change starts with behavior change established that it starts with behavior. Cultural resistance to change mapped the resistance. Designing cultural feedback loops designed the feedback loops. This lesson integrates these insights into a methodology: gradual, evidence-based, feedback-informed cultural evolution that works with the sedimentation dynamic rather than against it. The connection to schema evolution in organizations is foundational — this lesson is the cultural application of the schema evolution principles established at the organizational schema level. Look forward to Culture as executable infrastructure means it runs the organization, which closes Culture as Infrastructure with the integrative insight: when culture is well-designed as infrastructure, it runs the organization with minimal enforcement — producing aligned behavior as an emergent property.

Practice

Design a 12-Month Cultural Evolution Timeline in Notion

Create a structured 12-month cultural evolution plan in Notion that tracks a gradual cultural shift through pilot phases, evidence collection, and expansion. This practice builds the discipline of patient, evidence-based cultural change.

15 minutesAdvanced
  1. 1Open Notion and create a new database called 'Cultural Evolution Plan' with four views: Timeline, Pilot 1 (Months 1-6), Pilot 2 (Months 6-9), and Integration (Months 9-12). Add properties for Phase, Start Date, End Date, Context, Evidence Type, and Status.
  2. 2In the Timeline view, create your first entry for Months 1-3: document the current cultural pattern you want to evolve, the desired pattern, and identify one specific context (team, project, or process) where you can pilot the change. In Notion, use a toggle list to capture 3-5 reasons why this context is ideal for piloting without disrupting the broader organization.
  3. 3Create a second database page for Months 3-6 titled 'Pilot Evidence Collection' and build a feedback loop structure: add a table with columns for Date, Observation, What Worked, What Didn't Work, and Required Adjustment. Set up a recurring reminder in Notion to log evidence weekly, ensuring you capture at least 12 data points across the pilot period.
  4. 4Build a third page for Months 6-9 titled 'Pilot 2 Expansion' and create a linked database relation to your Pilot 1 evidence. Document which lessons from Pilot 1 you're incorporating, what you're changing in the approach, and which new context you're expanding to. Use Notion's timeline view to visualize how Pilot 2 overlaps with integration planning.
  5. 5Create a final page for Months 9-12 titled 'Cultural Pattern Integration Framework' with two columns: 'When Old Pattern Applies' and 'When New Pattern Applies'. Populate this framework based on your pilot evidence, explicitly recognizing contexts where each pattern has value. Add a 'Resistance Indicators' section where you track signs of rushing the evolution too quickly, with a checkbox to review this weekly.

Common questions about this lesson

More around this idea