The importance of disagreement within a team.
Disagreements are necessary for success. It serves as a warning that something wrong might be going on, along with how you form innovation, get a better sense of the landscape, and ultimately improve your product. You never want to surround yourself with like-minded people, else you risk forming an echo chamber.

When it comes to managing a team, it’s important to reward disagreement and have a system that allows disagreements to come earlier in the development cycle, rather than later. The earlier a disagreement is sorted out, the more time you save and the more rational you are able to think. Let me give you a scenario; you and your other team member worked on some code that completes one function. However, another member wants to pivot and do things a different way. In this scenario, it’s hard to logically think through the pivot because of how much time was already dedicated to the current, potentially flawed, solution. If this had been brought up earlier, time would have been saved.

However, you shouldn’t pivot every time a disagreement pops up. It’s important as the leader to have the vision and to make sure that resources are not misallocated and that the project stays on track to completion. Form a strong vision of what you want, but adapt it as you gain more information. Then use this new understanding to decide whether or not you need to pivot.