The yet-to-be-named federal chief technology officer will likely face a variety of challenges in executing the mission envisioned by President Barack Obama, according to a Congressional Research Service report released this week. Among the early hurdles will be negotiating domains of responsibilities, formal and informal, within the White House and with executive branch agencies that have overlapping missions. Obama has not indicated whether he intends to establish a CTO position by executive order or other administrative process, or whether he will seek legislation.
Congress may decide to provide a statutory foundation for a CTO, define the individual's roles and authorities, authorize and appropriate funds, provide for oversight, and address other aspects of the position, the CRS report dated Jan. 21 states. If Congress takes this route, questions may arise. What mission, duties, and authorities should the CTO have? Should a CTO serve as the chief CIO for the government as well as the lead champion for U.S. innovation? Should the CTO's appointment be subject to Senate confirmation? What is the relationship between the CTO and the existing CTOs and CIOs of individual agencies?
New Media
Online Politics
Tech Policy
Comments
To post a comment, you must provide a name and a valid e-mail address. Messages must be limited to 400 words. By using this service you agree not to post material that is obscene, harassing, defamatory, or otherwise objectionable. Although Tech Daily Dose does not monitor comments posted to this site (and has no obligation to), it reserves the right to delete, edit, or move any material that it deems to be in violation of this rule.