I'm spearheading a big initiative to deploy a system that significantly improve productivity and therefore reduce the number of field technicians needed to service our equipment. This is a typical type of project that I have worked on throughout my career, which means that it shares many common aspects and has its unique characteristics.
Despite industry best practices, we are going in violating quite a few things: big-bang rather than incremental rollout, end date set before details are understood, and resources are severely limited. The scope is clear (at least at this point). Despite my protests, I have been assured that my team will be supported, and we need to accept this as a challenge. I don't know why, but I agreed to push forward. I plan on documenting decisions, changes, and plans very well.
Saturday, June 30, 2007
Saturday, April 08, 2006
Life of an IT Manager
It's never a dull moment as an IT Manager. The job is a cross between a doctor, firefighter, psychologist, politician and gambler all rolled into one.
After many years in various capacities within IT, I am growing comfortable in recognizing and responding to the various issues that are a part of the job. I have to say that the early years were highly stressful and everything I did I felt I had to create a new process, template, or response; it required deep insight and heavy thinking. It's like when you make your opening in a game of chess, and the opposing player makes a very strange response (called a non-book opening). It takes some deep thinking to know how to respond correctly; if your opponent made an accepted book opening, your response is fairly documented and written about in many books on the subject (you just have to remember what it was!).
Anyway back to the thought: the early years and some of the mid years required thinking through the current situation, the risks, contingencies, strategies, and responses. I'm not saying it doesn't require thinking now a days, but certainly I have a "tool belt" of experiences to draw upon. And many templates, documents, and articles I've saved over the years.
So my job is enjoyable at this stage of my career. I get paid well, have a decent amount of autonomy and authority, can choose many of the people I work with (my team), and feel I have something to contribute. All very meaningful for me.
In the future, I may comment more on some of the career experiences I've learned.
After many years in various capacities within IT, I am growing comfortable in recognizing and responding to the various issues that are a part of the job. I have to say that the early years were highly stressful and everything I did I felt I had to create a new process, template, or response; it required deep insight and heavy thinking. It's like when you make your opening in a game of chess, and the opposing player makes a very strange response (called a non-book opening). It takes some deep thinking to know how to respond correctly; if your opponent made an accepted book opening, your response is fairly documented and written about in many books on the subject (you just have to remember what it was!).
Anyway back to the thought: the early years and some of the mid years required thinking through the current situation, the risks, contingencies, strategies, and responses. I'm not saying it doesn't require thinking now a days, but certainly I have a "tool belt" of experiences to draw upon. And many templates, documents, and articles I've saved over the years.
So my job is enjoyable at this stage of my career. I get paid well, have a decent amount of autonomy and authority, can choose many of the people I work with (my team), and feel I have something to contribute. All very meaningful for me.
In the future, I may comment more on some of the career experiences I've learned.
Tuesday, April 04, 2006
Go Live
The first blog entry is the most exciting, I suppose. It's the thrill of creating a space for my own musings and putting it out for the whole world to see (or the 3 people that decide to drop by).
In this space, my plan is to write about my experiences, thoughts, and outlook from my perspective. Being a senior manager in IT, my perspective will obviously be slanted, and I realize that. However my aim is to write about the things that interest me in the hopes of gaining clarity of my jumbled thoughts. If you find them of interest, then I'm pleased. Drop me a comment, whether in agreement or opposition -- either way you are welcome.
In this space, my plan is to write about my experiences, thoughts, and outlook from my perspective. Being a senior manager in IT, my perspective will obviously be slanted, and I realize that. However my aim is to write about the things that interest me in the hopes of gaining clarity of my jumbled thoughts. If you find them of interest, then I'm pleased. Drop me a comment, whether in agreement or opposition -- either way you are welcome.
Subscribe to:
Posts (Atom)