Commentary

Rob Preston
VP & Editor in Chief, Informationweek  

With Federal CIO, Obama's Off To A Decent Start, But ...

Thanks for listening, President Obama. The responsibilities you've carved out for Vivek Kundra, your newly appointed federal CIO, are roughly in line with those I recommended in a recent column. Now the devil is in the execution.

Thanks for listening, President Obama. The responsibilities you've carved out for Vivek Kundra, your newly appointed federal CIO, are roughly in line with those I recommended in a recent column. Now the devil is in the execution.The worry was that you'd task your top tech official with so many priorities that he wouldn't know where to start. Instead, Kundra -- former CTO of the District of Columbia -- will focus on how government agencies buy, use, manage, and coordinate information technology. That's still a monumental undertaking, of course, but at least you've set aside the weighty matters of national IT policy and competitiveness for a separate federal CTO, still to be named. (I had recommended that you leave those broad policy matters to the Commerce Department, specific agencies, and/or private sector leaders, but I'll reserve judgment on your federal CTO plan pending your filling that position.)

Mr. President, I had asked you to pick someone "who knows his or her way around Washington, but not someone so grounded in 'government IT' that fresh thinking becomes impossible." You've delivered. Before he was named D.C.'s CTO almost two years ago, Kundra, now 34 years old, served as assistant secretary of commerce and technology for Virginia, and earlier he had served as director of infrastructure technology for Arlington, Va. -- so he knows the local ropes. Kundra made his name, in part, as an early adopter of Google's Web-based apps and as a proponent of open source, social networking, and other cutting-edge technologies. And Kundra's portfolio management approach to projects seems especially relevant today. As the D.C. CTO, he hired a team of analysts to track projects, bundling the smaller ones into "funds," killing the ones going nowhere, and freeing up capital for those with the most upside. There will be plenty of opportunity for Kundra to exercise that disciplined approach across government agencies.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Mr. President, I also had recommended that you "lean toward a practitioner, a multinational CIO or someone with similar chops who understands tech architecture, purchasing, deployment, management, systems integration -- and people leadership -- on a massive, visionary scale." Here, Kundra's resumé is fairly short. In D.C., he ran a 600-person staff and oversaw 86 agencies, but it wasn't a world-class IT organization. Earlier in his career, as VP of marketing for Evincible Software, which specialized in identity management, and as CEO of Creostar, where he advised clients on IT governance and strategy, he did gain experience with how technology is developed and sold, but those were small, niche companies.

I also advised you to clearly define the responsibilities of your federal IT leader. It's reassuring that you're now separating oversight of government agency IT (fed CIO) from the more wonkish IT trade, innovation, and labor issues (fed CTO). But I hope you're not just creating more red tape. Please resist the temptation to attach the "czar" label to your CIO or CTO. (Czars didn't work out in imperial Russia, much less in the capitalist/socialist U.S.) Put your tech chiefs in a position to get things done, not just ruminate about frameworks and courses of action.

Terrific that the fed CIO reports to you, Mr. President, and not some political hack. As you put Kundra to work, we await your appointment of a fed CTO and your thinking on how the two will work together to make this country an IT leader in practice and industry. Keep us posted.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links