A Federal Chief Technology Officer in the Obama Administration: Options and Issues for Consideration

In November 2007, Senator Barack Obama announced his intention, if elected president, to appoint a federal chief technology officer CTO. He also identified several specific areas of responsibility of the CTO including transparency of government operations, computer and network security sometimes referred to as cybersecurity, identification and adoption of best technologies and practices by federal agencies, and interoperability of emergency communications technologies for first responders. On April 18, 2009, President Obama appointed Virginia Secretary of Technology Aneesh P. Chopra to serve in the newly created position of federal chief technology officer. In announcing the appointment, the president indicated that Mr. Chopra would undertake roles beyond what might be considered traditional CTO responsibilities. As the president described them, these roles include promoting technological innovation to help the United States create jobs, reduce health care costs, protect the homeland, and address other national goals. Mr. Chopra serves as assistant to the president and chief technology officer, as well as associate director for technology in the White House Office of Science and Technology Policy. Under a provision of Executive Order 13500, issued on February 5, 2009, he also serves as a member of the White House Domestic Policy Council in his capacity as assistant to the president and CTO. The CTO may face a variety of challenges in executing the mission envisioned by the President. Among the early challenges will be negotiating domains of responsibilities within the White House and with executive branch agencies that have overlapping missions. Some commentators have expressed concerns about the impact the creation of a CTO might have on existing offices and agencies with respect to the allocation and coordination of authorities and responsibilities.