Government chief information officers looking to exercise authority wisely can be easily undone -- by senior leaders who don’t understand the value of improved technology, by contracting rules that diminish that value or for a host of other reasons, officials said on Thursday.
The Association for Federal Information Resources Management asked a panel of federal CIOs and other top technology officials to reflect on how the CIO role has changed since it was officially instituted by the 1996 Clinger-Cohen Act and where the role stands today.
Here’s what they said:
CIOs can wield more or less power; It all depends on agency leadership.
“I think the CIO matters as much or as little as the deputy secretary and the secretary and the [chief financial officer] think the CIO matters,” Commerce Department CIO Simone Szykman said. “The actual strength of empowerment in Clinger-Cohen is somewhat limited. So the ability of the CIO to develop a vision and execute that vision comes down largely to the support we get from higher up in the agency leadership.”
But that authority won’t last if CIOs don’t make the most of it.
Karen Evans, national director of the U.S. Cyber Challenge and former e-government administrator during the Bush administration, described attending top agency leadership meetings as Energy Department CIO earlier in her career.
“If I go into that first meeting and it’s death by PowerPoint or I go in and I say here are all the things you can’t do and, by the way, I want control of every budget dollar [for IT] that is in this department, do you think I’m going to be invited back?” Evans asked. “When you get that one shot you’ve got to figure out a way to use it that brings everyone along with you to accomplish the goal.”
But even great ideas and strong support from on top can be undone by inefficiencies.
“The reality is you can’t lead what you don’t have,” said Paul Brubaker, director of planning and performance management at the Defense Department. He noted that long delays in personnel hiring can make technology management inefficient, sometimes delaying hires by two months or more.
“It’s just an insane way to run an organization, let alone a government,” he said.
Federal Communications Commission CIO David Bray described how acquisition requirements can often make it difficult to buy even simple goods and services. When the FCC tried to buy a $99 iOS developer’s license, for example, he was told that language in Apple’s terms and conditions meant the agency would have to go through the much more onerous process of developing a purchase order for the service.
“You can have the backing and you can even have the budget but you still have to work through procurement and you’ve still got to work through [human resources],” Bray said. “It’s fascinating that procurement -- and I don’t necessarily think it should be underneath the CIO -- but oftentimes that is the stopgap.”
Ethics requirements and presumed ethics requirements around CIO contact with vendors can also make the role extremely complicated Brubaker said, as can the fear of angering overseers and regulators.
He spoke specifically about agency paranoia following the General Services Administration’s much-publicized 2012 conference spending scandal.
“I’m telling you, we’re spending more money on reporting around conferences than we wasted in Las Vegas,” he said. “It’s unbelievably nonsensical how we’re chilling innovation, how we’re chilling free exchange, how we’re chilling what I would call intellectual curiosity,” he said. “And what we’re creating are these echo chambers…It’s a culture of fear, not just risk aversion but fear.”
Want to know what kind of tech executive you are? Take Nextgov's Challenge: Federal Tech.