Over the past few months, I have decided that my blog needed a little attention. The focus of what I’m going to be writing about has shifted from deep coding concepts to more of a focus on leadership, the agile movement, and IT organizational strategy.
A lot of folks that I work with tell me why they may not want to write a blog is the reason that they may not feel like an expert and therefore not qualified to be published online. The phrase, “Who would want to read what I have to say” is a common refrain back at Polaris Solutions. Acknowledging that own insecurity in myself, I feel like it’s important to share not only the “answer,” or destination – but it’s important to talk through the journey as well. And to that extent, I consider what I write and share with you to be lessons learned, mistakes, and observations as I grow myself.
Most paramount in my purposes here is that there may be a chance that some of this is something that you, the reader, can relate to. Possibly you’re seeing some of the same things in your organizations. Maybe even there’s a chance it helps you avoid the pitfalls that I’ve fallen into. To the extent that happens is rewarding to me. If you can relate to anything I write, please feel free to share in the comments.
“Work In Progress” is a title that really rings to me. Rather than any talk of Ivory tower, it’s more important to communicate that this is my goal. This blog really is a work in progress. My knowledge in the area indeed is also very much a work in progress. I am a work in progress.
Admittedly, I root for my home town – St. Louis, MO. It’s a great place to work and live. Additionally, I chose to include the Gateway Arch because like Agile, it’s simple and it represents reaching for new heights. It reminds me that solutions that work don’t necessarily need to be complex – in fact they’re better when complexity is gone.