If you’ve ever tried to introduce a new tool, technology or technique into an existing team, you’ve probably been met with resistance. Chances are, you’ve been told “no.” with no real discussion.
It’s a natural reaction for people to not want change. There’s potential risk. There’s learning curves. There’s a lot of emotional attachment to the way things are, and more.
If that’s the case, though, how do we bring new tools and technologies into a team?
In this episode of ThoughtsOnCode, I’ll share the technique that I’ve used in multiple companies, with multiple teams.