Commentary

Bob Evans
Senior VP, Global CIO  

10 Questions Our New Federal CIO Needs To Answer

UPDATE: Bob Evans has posted a new column on this subject called "The $200-Million-A-Day Man: Our New Federal CIO." You can read it here. It will be fascinating to see if newly minted federal CIO Vivek Kundra can establish a meaningful agenda, command the respect (or if necessary the fear) among the myriad agency CIOs he'll be trying to herd, and sooner rather than later get beyond such vague chatter as "improving citizen participation" and "promoting interoperability." Here are 10 questions to help our new federal CIO gain some focus.

UPDATE: Bob Evans has posted a new column on this subject called "The $200-Million-A-Day Man: Our New Federal CIO." You can read it here. It will be fascinating to see if newly minted federal CIO Vivek Kundra can establish a meaningful agenda, command the respect (or if necessary the fear) among the myriad agency CIOs he'll be trying to herd, and sooner rather than later get beyond such vague chatter as "improving citizen participation" and "promoting interoperability." Here are 10 questions to help our new federal CIO gain some focus.1) Who's your boss? In the private sector, it's much better to report to the CEO than the CFO. This morning, the Washington Post said you "will operate under the auspices of the White House." While such piffle might play well inside the Beltway, folks elsewhere will want to know what the heck does that mean?

2) How many CIOs will be reporting to you? And is that a straight-line reporting structure so that you have at your disposal an oak paddle (not an oar-type paddle, but a whipping-stick-type paddle) with holes drilled for greater acceleration? Or will you have a dotted-line structure that arms you with conflict-resolution pamphlets?


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

3) Who are your direct reports? How big is your staff? Your public comments today were sprinkled with stuff about visibility and transparency and such -- so who's on your team, and what are they responsible for achieving?

4) What's your plan for your first 100 days? What project will you tackle first?

5) By what metrics will your performance be judged? And by whom? And how will that measure up to the pledges we keep hearing about "the most transparent administration ever"?

6) To fix the apparently intractable IT disasters at the IRS and FBI and other places, will you consider using U.S.-based companies who happen to have (as many thousands of companies do here in 2009) employees in other countries? For example: Google, IBM, Microsoft, Hewlett-Packard, Accenture, Oracle, EMC, Cisco, Symantec, Cognizant, and many many more?

7) Will you commit up-front to cutting the $71 billion budget that the federal government somehow, some way, managed to spend on IT in 2008?

8) What, if any, oversight will Congress have over you and your team? These days, Congress is insinuating itself into every facet of the daily lives of Americans -- how will you or your "controlling auspices" be able to ward off that type of smothering assistance?

9) How would you describe the ways in which your role and that of the proposed CTO will (a) complement each other; (b) be completely distinct from one another; and (c) have to be carefully calibrated to ensure everyone on both teams is striving to reach the same goals?

10) Before you immerse yourself too deeply into some severely hairy projects that you and you alone in all the world are capable of overseeing, we must ask: have you paid all your income taxes?

Good luck, Mr. Kundra, and remember: keep your friends close but your enemies closer.


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