Getting his point across about the role of CIOs
John Kost believes passionately in the role of chief information officer. Many years of experience convince him that state bodies need a strategic approach to IT, writes KARLIN LILLINGTON
THE ROLE OF chief information officer remains one of the most poorly understood within government organisations worldwide – when it exists at all.
So says John Kost, a group vice-president at analyst Gartner and a determined man who has set out to change the misunderstanding. He knows what he’s talking about – he was the first-ever state CIO in the US, in Michigan, over 20 years ago.
He now spends his time talking at very high level to governments internationally, and was recently here to advise the Irish Government about large-scale projects and the role of CIO – a position the previous government considered creating. Many countries do have CIOs, he says, noting that Israel has just established such a position.
Kost readily admits he was, at least under common assumptions about the role, an unlikely candidate for CIO. He had no background in information technology, and at the time, worked for John Engler, the Republican governor of Michigan, as head of policy.
“He wanted to make radical changes, but was frustrated,” says Kost. “The message he was getting was that the technology was too old to do the things that he wanted to do.” So, the governor asked Kost: “How do we turn IT into an asset, rather than a liability?”
Kost consulted large, Michigan-based companies such as Kmart, Ford and Dow to talk to their corporate chief information officers about how they used and managed their IT.
“And they said, you need a CIO.” So Kost went back and told the governor that Michigan needed a statewide CIO: not somebody who would only be in charge of IT, but someone who would take infrastructure management away from the departments and let them focus on applications development, business processes and customer focus.
“He came back and said, ‘I love the plan – and I want you to be the CIO’,” laughs Kost.
Kost made significant changes in how IT was managed, based on best practice in the corporate world, as well as shaping information-based strategy. He says the key lesson that he took away from his time as CIO – he was there until 1996 – was that the CIO has to respond to the type of person in the leadership role of the organisation.
Unfortunately, he says, many organisations still do not view the CIO as a strategic position and instead, consign him or her to a kind of high-level IT management position with little buy-in at board level. At the same time, many traditional CIOs, from strong IT backgrounds, are more comfortable simply managing the technology, and far less comfortable with managing business processes and innovation in the organisation.
The inclination of government leaders can be to make the CIO role a basic managerial role. “IT makes news a lot – it’s often the failure of an IT project that makes headlines – so political leaders often create the CIO role to make technology go away.”
Usually, governments and semi-state organisations have a pretty good idea of why they need a CIO, he says, and his own job tends to be helping them to determine what type of CIO they want. “They can be anything from a VC to managing IT; they can do broad-level policy or specific niches. The question I ask is, what do you want to accomplish politically? You need to be very clear in your mind what problems you want solved.”