Coevolution of Practice

Coevolution of Practice is the ongoing interplay between evolving practices and the changing characteristics of the components they depend on. As technology and context evolve, methods that once worked become less effective, and new practices emerge to fit the new reality. This pattern removes confusion when "old" and "new" coexist.

Why it matters

• Removes confusion: Helps teams recognize when they’re using outdated practices on evolved components.
• Supports better decisions: Makes clear why new approaches are required as characteristics shift from custom-built to commodity.
• Explains conflict: Different stakeholders adopt change at different speeds; resistance often reflects sunk costs or familiarity with prior methods.

Examples

• Cloud → from ITIL to DevOps: Cloud compressed provisioning from weeks to seconds. Traditional server management practices (e.g., ITIL) no longer fit the new characteristics; DevOps emerged to match them.
• Energy & Appliances: Pressure to reduce CO2 and rising energy costs are changing how we use home appliances, driving more sustainable, data-aware practices.
• Social Media & Speech: Algorithmic amplification changes the landscape of “reach,” forcing new norms and governance around expression and responsibility.

Conflict is expected

Adoption is uneven. Those invested in prior methods may resist or feel threatened. Expect a spectrum from confusion to hostility. Being able to spot coevolution and explain it clearly to executives is a valuable consulting skill.

How to use it in mapping

• Identify component characteristics: Map components and note where they sit on evolution (Genesis → Custom → Product → Commodity).
• Check method fit: Ensure practices match the component’s characteristics (e.g., agile for uncertain/novel; lean/six sigma for industrialized).
• Plan transitions: When components evolve, plan the corresponding practice shift and enable teams to learn the new approach.
• Communicate trade-offs: Make coexistence visible when both old and new exist (e.g., hybrid environments) and set expectations.

Key insights

1. Practices must evolve as components evolve.
2. Mismatched practices create waste, delay, and frustration.
3. Coexistence phases are noisy—clarity reduces conflict.
4. Education and explicit transition planning accelerate adoption.

Conclusion

Coevolution of Practice explains why “what worked before” stops working as context changes. By mapping components and aligning practices to their current characteristics, organizations reduce friction, improve delivery, and make better strategic choices.

—

Learn more in related entries: Evolution Stages, Doctrine, Value Chain, and ILC.