xsevensinzx (10/23/2016)

---

David.Poole (10/22/2016)

---

5. Not putting the team first.

Actually, I slightly disagree with this. I feel conflict happens a lot because people are putting the team first over the business. We all work for the business, we don't work for ourselves. Countless times, I've seen people put their own careers and their teams first over doing what's right for the business. This is bad.

Unfortunately, when you talk about topics like that, many understand that as you as a employee are not important to the business. That you have to give everything to the business to where it burns you out. That's not the meaning here. It just means we always have to be thinking about the business TOO. At some point, you will have to make decisions that are hard for you and your team too, but it's the right decision for the business.

For example, I've ran into issues where certain technologies were not considered because it could mean not using a technology favored by majority of the team. This leads team members to have concerns of their value on the team, concerns with new challenges and even concerns with the future of role with the business. When we treat all problems as nails and certain technologies as the hammer that can fix all, we sometimes lose sight of what's best for the business because we are only thinking about ourselves or the teams value. (i.e.: instead of using SQL Server to fix this problem, let's use this X solution instead!)