Introduce Change as an Evolution, Not Revolution

Recognize that challenging someone’s methods can feel like an attack on their professional identity or core beliefs. Introduce change as a small differentiator or evolution of their existing model, rather than a complete replacement. Meet people where they are to avoid triggering a defensive reaction and allow for gradual adoption.

Examples

If a team is committed to UML, start by using their existing diagrams collaboratively before introducing a completely different technique. This respects their current model while gently evolving the collaborative practice.