Jan 052011

I have just finished reading recent blog posts from John Hughes and Peter Kretzman. Both blogs are well written and have excellent CIO material since both men have served as CIOs.

Trust Me, I’m the CEO

John discusses the concept of trust in his post Trust me, I’m a CIO and in particular, being glued to the CEO means that you develop relationships with key stake holders. I would add that managing key stake holder relationships is the critical to develop and to manage credibility. How do you know if you are credible unless you are actively asking the tough questions of your peers where their perception of how you are doing your job is so critical. More incites from John can be found here.

Are You a Scrappy CIO?

Peter’s use of analogy in his blog Mending Wall: Matches and mismatches in IT stakeholder expectations is very cool and I won’ steal all his thunder in my synopsis however there are a few points I would like to make. Similar to Peter, I think it is so important for IT executives to VISUALLY represent to the stakeholders what Peter describes as “metering lights on the freeway” – sort of like educating them using the examples of “red light, green light and yellow light.” We all receive data and information differently. What if you shifted your communications approach to stake holders with pie charts, graphs, pictures? I also loved Peter’s analogy of “Being Scrappy” and looking to de-couple deliverables to get chunks of projects done…so critical. I believe this dove tails nicely with John’s point about relationship building and showing a stakeholder how you can make something happen for them! It is important to make the stakeholders happy, but as Peter mentions, it is necessary to also have fences and boundaries. Just make sure you build fences that are chest high so you can talk over them!

Dec 142010

I came across a great blog post – Business Impact and Transparency: Expressing System Availability – written by Peter Kretzman, former CIO with PlanetOut, Inc. and Compography. He has a more elegant title than the one I posted in the subject line, but he writes in a way that makes sense in communicating the business impact and expressing system availability.

How many times have you heard that your tech guy thinks the systems are up but the business folks still can’t use the system. The email system is ‘up’ so says your tech, but the Internet line is down so no external or internal users can access email via Blackberry, OWA, etc. A high impact situation for sure, but not necessarily a system that drags revenue.

Interested in your thoughts on how Peter addresses this vital communication task…