As the year ends, I've spoken to many CIOs. 2011 was a hard year filled with Meaningful Use (including many upgrades to certified systems or self-certification), 5010 (the deadline for upgrading billing systems is January 1, 2012), accelerating compliance demands, new security threats, rapidly evolving technologies, and unprecedented demand for new projects driven by the consumerization of IT.
At the same time that CIOs and IT professionals are running marathons, they are being held accountable for events that are not directly under their control. They are not being congratulated for the miracles they create every day, but are being criticized for not moving faster.
What do I mean?
One CIO received a negative audit report because new generations of viruses are no longer stopped by state of the art anti-virus software. Interesting. The CIO cannot control the virus authors, nor the effectiveness of anti-virus software. No one in the industry has solved the problem, but audit firms revel in creating fear, uncertainty and doubt at the Board level as it enhances the reputation of the auditor.
Another CIO was held accountable for infrastructure demands that were not forecasted, planned, or communicated. CIOs do their best to be proactive, but in the world of Big Data, past trends may not predict future needs.
Another CIO was was given 10 goals and 5 unplanned urgent projects. She completed 8 of the planned goals and all the urgent projects, yet was told she only met 80% of expectations.
In a world that expects leaders to continuously perform miracles with constrained resources in limited time, we all need to step back and take our own steps to stop the madness.
With your own staff, celebrate the joy of success and focus on what really matters.
Did you achieve Meaningful Use?
Did you support compliance requirements on time to meet regulatory deadlines?
Did you maintain employee satisfaction and minimize turnover?
If so, you're an IT Leadership hero.
Did your Board or senior management note that a new application or website launched a few weeks late because you wanted additional testing time to minimize risk?
No one will ever remember.
Did you defer a "nice to have" project because an unplanned "must have" occurred mid year?
Good for you.