In any process, whether it’s code, leadership, team development, building, whichever, there is a part where it gets awkward.
Perhaps it’s a hypothesis that failed.
Maybe your design fell on its face.
Maybe the presentation on team growth fell flat.
Whatever it is, there is that awkward moment of silence where you can either look it in the eye and figure out how to fix or you can let it sit there, stare at it, get mad at it, blame everyone around you for it because “hey, I didn’t ask for this awkwardness”.
But if you can embrace it and realize that you’ll be better for it if you can work through it, you’ll come out that much stronger, that much smarter, and that much more prepared for it next time.
We can take awkwardness as being a bad thing OR we can embrace it for all the goodness it can deliver us.
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.