Should We Worry About A National CTO?

from the Czars-are-bad,-mmkay? dept

Here in D.C. the town's collective post-election hangover is lifting, and folks are beginning to ponder exactly what the new administration will mean for their respective corners of the world. Those of us working in technology are no exception, and a new blog post by Wayne Crews on OpenMarket.org has renewed discussion of President-elect Obama's proposal for a national CTO.

Unfortunately, Crews' post doesn't offer much insight — he simply conflates "CTO" with "czar" (as in "drug czar") and then decides that the track record of such positions means the initiative is a bad idea. As Jerry Brito noted in comments at the TLF, this rhetorical sleight of hand is a bit dishonest. The Obama campaign's stated intention is for the CTO to "ensure the safety of our networks and will lead an interagency effort, working with chief technology and chief information officers of each of the federal agencies, to ensure that they use best-in-class technologies and share best practices." That's considerably less expansive than what Crews seems to fear.

Our own Tim Lee has weighed in on the idea before, defining two possible roles for a national CTO: one as a coordinator of federal systems (as described above) and another as an adviser on tech policy. As Tim notes, it's important that President-elect Obama receive smart counsel on tech policy — and the Obama campaign's association with people like Vint Cerf is encouraging on this score. But again, it's not clear that such advising is within the purview of the CTO role as Obama conceives it.

So what about the other function? Tim isn't enthusiastic about it, noting that the government probably already achieves what economies of scale it can, meaning that centralizing IT decisions would only result in reduced flexibility for individual agencies.

Speaking as a former government IT contractor, I'm not so sure about that. In my experience, IT procurement decisions within agencies are played very, very safe. The person making the purchasing decision is generally operating in CYA mode: the purchase is being made with an eye toward their career. There are no stock options or revenue sharing to consider — no upside — so the primary goal is to make decisions that minimize the potential for blame.

In practice this means buying from huge, established vendors, even when doing so isn't really appropriate. I've seen projects buy massively expensive Oracle licenses when MySQL or PostgreSQL would've worked just fine, and would have cost far fewer dollars and man-hours. Why waste those resources? Because Oracle was seen as safe (particularly since Sun hadn't yet acquired MySQL AB). It's the same old problem that slowed private industry's adoption of open-source software, except without the profit motive to push things along.

It's possible to mount a justification for such a cautious approach by government, but "efficiency" isn't likely to be part of that argument. And here's where a national CTO really could make a difference: the high-profile, appointed nature of the position calls for a big name — someone with influence and a proven record of innovative ideas — rather than a cowering careerist. And that, in turn, might embolden the don't-blame-me CTOs and CIOs further down the federal ladder. Desktop Linux springs to mind as the sort of technology that could save huge amounts of taxpayer money, but which is probably too intimidating for most agencies to undertake without direction from above.

What would this mean for you, me and the larger tech industry? In all likelihood, not very much. It's not as if open-source technologies need the government's stamp of approval to prove their viability; and every indication is that the important regulatory decisions that affect our industry will continue to be made at places like the FTC and FCC. A national CTO will be irrelevant to most of us, so time spent fretting over the office is probably time wasted. But that doesn't mean that such a position isn't a good idea — saving tax dollars usually is, and there's reason to think that a national CTO could do just that.

Tom Lee is an expert at the Insight Community. To get insight and analysis from Tom Lee and other experts on challenges your company faces, click here.

10 Comments | Leave a Comment..

Do We Need a National CTO?

from the maybe-not dept

The 463 blog points us to an interview with Mitch Kapor of Lotus and EFF fame, in which he makes the case for a national Chief Technology Officer. The idea seems to be that technology policy in the United States is currently fragmented among a bunch of different positions, and having a designated top technologist in the government would help to bring coherence to the nation's technology policy. It sounds like a reasonable idea at first blush, but on closer examination it might create more problems than it solves.

To start with, it's important to distinguish between two jobs that are really quite different. One job is to coordinate the government's own IT infrastructure. Currently, IT decisions are made by the various federal agencies and departments within the federal government. A national CTO could conceivably set guidelines or policies related to IT infrastructure that would apply across the executive branch. The other job is to advise the president on substantive tech policy issues like network neutrality, patents, copyrights, etc. The two jobs are very different, and it's not at all clear it would make sense to have the same guy doing both. But let's consider each position in turn.

It's not clear how significant the potential savings or efficiency gains would be from having a single guy in charge of all government IT deployments. Up to a certain point, there are efficiency gains to be had from greater IT integration, but the federal government is probably so large that those economies of scale have already been exhausted. That's especially true when we consider that the different parts of the government have widely different requirements. Some parts, such as the FBI and NASA, have offices all over the country, while others are located almost entirely in Washington. Federal agencies do different kinds of work and need a wide variety of software packages. The current arrangement, in which each agency manages its own IT infrastructure, seems likely to give each agency more flexibility to choose technologies that meet its specific needs.

The idea of a designated tech policy advisor is more promising, but that also has potential downsides. A good choice could help bring coherence and vigor to a president's tech agenda, but, given enough power, a bad choice could cause just as much mischief. Therefore, if the next president does create a CTO position, he ought to limit its function to advising the president, rather than pursuing an independent policy agenda. A good model for this is the president's Council of Economic Advisors, which advises the president on economic policy and produces an annual report on the state of the economy but doesn't wield any significant authority in its own right.

Timothy Lee is an expert at the Insight Community. To get insight and analysis from Timothy Lee and other experts on challenges your company faces, click here.

19 Comments | Leave a Comment..