Steve VanRoekel named new federal CIO

The Obama administration on Aug. 4 named Steven VanRoekel as the new Federal CIO, replacing Vivek Kundra.

President Barack Obama intends to appoint VanRoekel as Federal CIO and as administrator of the Office of Electronic Government in the Office of Management and Budget, according to a statement from the White House.

“I am grateful these accomplished men and women have agreed to join this administration, and I am confident they will serve ably in these important roles," Obama said of VanRoekel and several other appointees in the statement. "I look forward to working with them in the coming months and years."

VanRoekel appeared to confirm the appointment by listing his title as "United States Chief Information Officer" on his Twitter account (@stevenvDC). VanRoekel could not be reached directly.

FCC spent $1.4M to move website to cloud, go open source

VanRoekel said to be leaving the FCC after completing website revamp

He left the FCC in June, and recently has been serving as an executive director for the U.S. Agency for International Development, where he leads a citizen engagement and participation project.

Kundra, whose portfolio at the White House included programs for innovation, data center consolidation, cloud computing, IT management dashboards, segmented IT development and Web 2.0 platforms, recently announced he had accepted a position at Harvard University, effective this month.

VanRoekel came to the federal government from Microsoft Corp., where he held various executive positions for 15 years, including managing cross-industry Web services and serving as a speech and strategy assistant to Bill Gates.

While at the FCC, he was responsible for administration and management of budget and financial programs, personnel, telecommunications, fees, the Universal Service Fund, physical space and security, among other items.

His accomplishments there included restructuring the FCC website on open source Drupal technology, moving the website to the cloud, organizing data with Extensible Markup Language (XML) and Application Programming Interfaces (APIs) and initiating crowdsourcing discussions.

When he arrived at the FCC, the former FCC.gov website was sprawling and difficult to navigate, with 40,000 Web links available, which was confusing and lacking in organization for the average visitor, VanRoekel said at the OpenGovDC conference on June 14.

The FCC.gov website had won awards for excellence in the 1990s and had not been substantially updated since then, he said.

What was worse, the “404 message” Web page indicating an error or bad link was among the FCC.gov’s top five most visited pages, VanRoekel said.

Van Roekel said one of his greatest problems at the FCC was overcoming cultural inertia and listening to customers, especially the million unique visitors to the website each month.

One of the his assignments for his website revamping team was to visit with the FCC’s call center in Gettysburg, Pa., for a day to learn what types of information people calling the agency were seeking. He also applied crowdsourcing tools, performed a user survey and used internal blogs and other social media to engage FCC employees in the process of change.

VanRoekel said the commission spent $1.35 million on the revamp. The new site went live in May.

At the June 14 conference, VanRoekel also spoke more generally of his philosophy about how government and commercial technology companies can learn from each other, and he strongly advocates use of XML and API to foster collaborative systems.

He coined the “.cov” term to describe his aim of merging commercial and government domains into a new collaborative and efficient environment.

Developers should try to understand the specific challenges of government agencies and to help foster cultural change, he said.

Government managers need to strive for cultural change, leadership and legal expertise, he said.

He also urged federal IT managers to spend for XML and APIs as broadly as possible.

“Every piece of data should use XML,” VanRoekel said. “Every access should be an API.”