What do CIOs really do?

by billso on Thursday, 1 March 2007

I’ve been devel­op­ing the final exam for my IS 6100 stu­dents. It’s only March 1, but I’d like to have the exam posted by April 16, a date asso­ci­ated with another painful sub­mis­sion here in the USA.

Yes­ter­day I attended a web con­fer­ence about the roles of the CIO (chief infor­ma­tion offi­cer).
In many North Amer­i­can orga­ni­za­tions, the IT direc­tor role is migrat­ing to a CXO posi­tion that reports directly to the CEO or president.

CIO reports to CEO
In IS 6100, we con­sider infor­ma­tion sys­tems and infor­ma­tion tech­nol­ogy in terms of tac­tics and strat­egy. The CIO has con­trol over both short-term and long-term decisions.

One inter­est­ing result of the sur­vey dis­cussed at this web con­fer­ence was that CIOs tend to spend most of their time man­ag­ing legacy and short-term issues, instead of strate­gic new tech­nol­ogy issues. It’s not sur­pris­ing that one noted researcher, C.K. Pra­ha­lad, has esti­mated that main­te­nance of legacy sys­tems accounts for as much as 85% of some IT bud­gets.
CIO 2007 pie chart

Christo­pher Koch may have been think­ing of this prob­lem when he wrote his post, “Why IT Sucks”. His dis­cus­sion addresses the wicked prob­lem that faces CIOs — bal­anc­ing con­flict­ing tac­ti­cal and strate­gic roles.

Ben Worthen coun­ters with an equally plau­si­ble argu­ment — IT doesn’t suck. Infor­ma­tion sys­tems suck — a lot. From clunky user inter­faces to com­pli­cated pro­ce­dures, more cor­po­rate users seem to feel that their IT depart­ment focuses more on man­ag­ing these sys­tems than mak­ing the user expe­ri­ence effi­cient effective.

Share

Previous post:

Next post: