Online Chat

Use the window below to chat with me (if I'm online ...)

Use the edit nick field above to let me see your name.

cazh1: on Business, Information, and Technology

Thoughts and observations on the intersection of technology and business; searching for better understanding of what's relevant, where's the value, and (always) what's the goal ...

Sunday, October 31, 2004

"New" Job, Same Location

"New" Job, Same Location

An unexpected event this past week - turnover at the top IT position here, as our CIO is moving on to another opportunity. It is a great move for him, puts him back into the (larger) size and scope of company that he has worked at in the past - congratulations all around.

The transition has been relatively smooth; the outgoing CIO, myself, and the lead Tech Ops guy have worked together a long time, and we have implemented effective communications and controls for IT here at Culligan, so none of the transition tasks have been much of a surprise.

As for myself, I am taking on lead IT duties for the company. Currently this is an interim role, as the President of the company needs to make evaluations, consider internal and even external options. I know this approach makes sense, contrary to what other folks may think; over the past 18 months, I've probably spent less than 5 hours in the same room as the President and executive staff, as they have been consumed with the process of selling the company and adapting quickly to the new management / reporting style of the new owners. They need to see and understand what my skills are at the "next level" - most have never had the chance until now.

I also am having to listen intently to my own coaching. With members of the IT team, I often spend time working on their communication styles - too many details, drive to the relevant points. Yet, the first feedback I got from the president (when we sat to review his intentions for the transition) was his perceptions on my communications style - too many details, drive to the relevant points.

An interesting look in the mirror, I must say, and even though I understand the why's and wherefore's, it's a refreshing chance to refocus. Hey - I've got a new boss, a new peer group, and a great opportunity to show I'm ready for the role; I need to develop an effective, audience-appropriate communication style.

Am I disappointed in not simply being given the role? Not really - for the very practical reasons discussed above. The executive team has never seen me perform in a Lead IT role, and my "existence" does not and should not immediately qualify me for the step up. Of course, I know I am ready for the role and am excited at the opportunity to show my capabilities in the void that now exists, but that's really how it should be. I realized this in conversations this week with some of my team, talking about their interest in my position. My reaction is the same as my new boss - I haven't witnessed any specific performance that indicates readiness / skill set for the role, so why assume that?

The end of the year beckons, challenges await - should be fun!

<< blog home