I wrote the other day about The cult of “My Three Words”. It’s a new year tradition among some early social media adopters, apparently started by Chris Brogan in 2006. Chris explains My Three Words this way:

Pick any three words that will guide you in the choices you intend to make for 2016. They should be words that let you challenge yourself as to motives and decisions. They should be words that help you guide your actions.

A quick reflection on 2015

2015 was a transformative year for me. There were plenty of challenges, and they motivated many changes. My experiences are still fresh, as are the lessons I learned. And, with the patience and support of those around me, the year ended on a significant high, setting the stage for an already strong start to 2016.

My three words for 2016

Ready – In his book An Astronaut’s Guide to Life on Earth, retired Canadian astronaut Chris Hadfield pulls back the curtain on his life, career path and the investment both he and his employers have made in him. One of the key takeaways is, in his line of work, everyone trains and rehearses everything — what to do and when, which tools to use and how, how to intelligently improvise, etc… — until they can do it all without impacting their heart rate or breathing patterns. I want to be “astronaut-ready” with all my tools and processes, and help others achieve the same.

Refine – Big changes do happen and are sometimes even necessary. That was 2015 for me. In 2016, I’ll take a more active approach to situational analysis. That likely means changing the way I use some of my tools (particularly the administrative tools) to make sure I’m fully aware of my surroundings and how I can make sure I get to where I’m going in the most efficient manner.

Results – I wholly enjoy the process of making something happen. Sometimes my own projects get impacted (read: drag) because I’m more invested in the process than the outcome. By focusing more on project results in 2016, I’ll ensure I consider the value of the project for me and for others before I make the go/no-go decision.

MB-HierarchyOfDev-2016