Would it be possible to go deeper in depth here?
Michael Malach
11

Hi Michael, there were a number of factors here that caused the product from being adopted:

1. Skill set: we were shifting from Java/JavaScript hybrid to full stack JavaScript using Node. In 2012, Node was still the new kid on the block and there was resistance to change. We were able to overcome this by training and educating the teams as part of the transition.

2. Competing Platform/Solution: there was another team that had a similar solution. They were unwilling to collaborate with us even though we were open to it. It got so bad we had to do a showdown of our tools with a sample app. Believe or not, our app was superior, however, politics ultimately prevailed. This leaves to #3

3. At the end of the day it lead to politics. And this experience taught me a valuable lesson in my career as how NOT to act as a leader. Here are my thoughts:

  • Always make sure the vision and strategy is clearly communicated. For those not aligned, they might need to find another position or role within the company (or a new job).
  • If there are duplicate solutions, consolidate. It is a waste of time and money to have two teams doing the same thing.
  • Politics destroy a healthy culture. As leaders we should focus on building strong relationships, ensuring there is a path forward towards efficiency.

In the end, it’s about understanding your environment and knowing when to quit and shift. Master this and you will be one step ahead of the game.