Should the United States' New CTO Really Be a CIO?
CurtMonash writes "Barack Obama promised to appoint the United States' first Chief Technology Officer. Naturally, the blogosphere is full of discussion as to who that should be. I favor American Management Systems founder and former IRS Commissioner Charles Rossotti. Richard Koman thinks it should be one of the better state CTOs. John Doerr, going in a different direction, thinks it should be his partner Bill Joy. We can bandy names back and forth all month, but first a more fundamental question needs to be answered: What do we need most — a get-things-done CIO (Chief Information Officer), or a more visionary true CTO? I think it's a CIO, and based on his campaign statements it appears Obama agrees. Management of government IT is a huge, generally unsolved problem, and we need somebody deeply experienced to have a fighting chance. Of course, that doesn't preclude recruiting a visionary CTO in addition, but the highest priority is a CIO. What do you think?"
Since this position is pretty much new territory for the government, and since there will likely only be a single position created, it will probably end up being a hybrid CIO/CTO position anyways. As for who it should be, the Rossotti suggestion seems fairly reasonable. My father has worked for AMS for the past 20+ years on a number of government contracts. The one thing he always comes back saying is how screwed up and redundant a lot of the setups are--it's layer upon layer of hackjobs just to get the various systems to talk to one another. Rossotti is well aware of the current state of technology affairs within the government. I'm sure there are plenty others like him, but he is definitely someone who would be in a position to help clean up some of the mess that's there.
This guy's the limit!
Flame-on!
Physics is nothing like religion. If it was, we'd have an easier time trying to raise money!