Yesterday’s unit test results.

Last week’s build breakage.

Last month’s bad update.

Last year’s roll-out that went sideways and didn’t make it in until the third try.

These alone aren’t bad when they occur, but when we hold onto them, reference them in meetings when someone wants to try something new, test out a new idea or approach and use them as justification for not implementing change.

This is when they become our biggest failure.

Holding onto what didn’t go well for you yesterday is a surefire ticket to never let your team grow, never let yourself grow and never have the opportunity to see what could actually be.

Like the song says, “Let it Go”, you’ll feel better for it.

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