Heuristics

Introduce Change as an Evolution, Not Revolution

Authors: Paul Rayner, Andrew Harmel-Law, Kenny Schwegler, Andrea Magnorsky

Submitter: Andrea Magnorsky

How can we introduce new ideas that conflict with a team member's deeply held beliefs?

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.

 

Tags

Follow us

Read our latest news from Virtual DDD on any of these social networks!

Recent heuristics

Discussed content

Sorry, no results found!

Whoops... we couldn't find what you're looking for