It’s not before the project starts – that would be too upsetting to the team, let’s see how things get going first, we don’t want to slow things down?

It’s not during the project – well the team is already working towards the next release, wouldn’t this slow them down?

It’s not near the end of the project – well things could be doing better, we are late, but if we switched now wouldn’t this slow us down even more?

So if it’s none of those times when would you recognize a problem with leadership?

The fear of slowing things down isn’t a reason, it’s an excuse to keeping hoping for things to get better.

The problem is if you know it at the start, leaving it alone is only going to make it worst in the end.

Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).  I’m also the co-host of the Remotely Prepared podcast.


Write A Comment