US CTO Park to step down, move west to recruit for Uncle Sam

IMG_0507.JPG

United States chief technology officer Todd Park will be moving to California at the end of August, just in time to take his kids to the first day of school. He’ll be shifting from his current position in the Office of Science and Technology a Policy to a new role in the White House, recruiting technologists to join public service. The move was first reported in Fortune Magazine and then Reuters, among other outlets. Update: On August 28th, the White House confirmed that Park would continue serving in the administration in a new role in blog post on WhiteHouse.gov.

“From launching the Presidential Innovation Fellows program, to opening up troves of government data to the public, to helping spearhead the successful turnaround of HealthCare.gov, Todd has been, and will continue to be, a key member of my Administration,” said President Barack Obama, in a statement. “I thank Todd for his service as my Chief Technology Officer, and look forward to his continuing to help us deploy the best people and ideas from the tech community in service of the American people.”

“I’m deeply grateful for Todd’s tireless efforts as U.S. Chief Technology Officer to improve the way government works and to generate better outcomes for the American people,” added White House Office of Science and Technology Policy Director and Assistant to the President John Holdren. “We will miss him at the Office of Science and Technology Policy, but we’re fortunate Todd will continue to apply his considerable talents to the Obama Administration’s ongoing efforts to bring the country’s best technologists into the Federal Government.”

It will be interesting to see how Park approaches recruiting the nation’s technologists to serve in the new U.S. Digital Service and federal agencies in the coming months.

“It continues to be the greatest honor of my life to serve the President and the country that I love so very much,” stated Park, in the blog post. “I look forward to doing everything I can in my new role to help bring more and more of the best talent and best ideas from Silicon Valley and across the nation into government.”

For a wonderfully deep dive into what’s next for him, read Steven Levy’s masterfully reported feature (his last for Wired) on how Park is not done rebooting government just yet:

Park wants to move government IT into the open source, cloud-based, rapid-iteration environment that is second nature to the crowd considering his pitch tonight. The president has given reformers like him leave, he told them, “to blow everything the fuck up and make it radically better.” This means taking on big-pocketed federal contractors, risk-averse bureaucrats, and politicians who may rail at overruns but thrive on contributions from those benefiting from the waste. It also will require streamlined regulations from both the executive and legislative branches. But instead of picking fights, Park wants to win by showing potential foes the undeniable superiority of a modern approach. He needs these coders to make it happen, to form what he calls a Star Wars-style Rebel Alliance, a network of digital special forces teams. He can’t lure them with stock options, but he does offer a compelling opportunity: a chance to serve their country and improve the lives of millions of their fellow citizens.

“We’re looking for the best people on the planet,” he said. “We have a window of opportunity—right the fuck now—within this government, under this president, to make a huge difference.

“Drop everything,” he told them, “and help the United States of America!”

Who will be the new CTO?

The next US CTO will have big shoes to fill: Park has played key roles advising the president on policy, opening up government data and guiding the Presidential Innovation Fellows program and, when the president asked, rescuing Healthcare.gov, the federal online marketplace for health insurance. While it’s not clear who will replace Park yet, sources have confirmed to me that there will be another U.S. CTO in this administration. What isn’t clear is what role he (or she) might play, a question that Nancy Scola explored at The Switch for the Washington Post this week:

There’s a growing shift away from the idea, implicit in Obama’s pledge to create the U.S. CTO post back in 2007, that one person could alone do much of the work of fixing how the United States government thinks about IT. Call it the “great man” or “great woman” theory of civic innovation, perhaps, and it’s on the way out. The new U.S. Digital Service, the pod of technologists called 18F housed at the General Services Administration, the White House’s Presidential Innovation Fellows, even Park’s new outreach role in Silicon Valley — all are premised on the idea that the U.S. needs to recruit, identify, organize, and deploy simply more smart people who get technology.

An additional role for the third US CTO will be an example of the Obama administration’s commitment to more diverse approach to recruiting White House tech staffers in the second term. The men to hold the office were both the sons of immigrants: Aneesh Chopra is of Indian descent, and Park of Korean. As Colby Hochmuth reported for Federal Computer Week, the White House of Office and Science and Technology Policy achieved near-gender parity under Park.

If, as reported by Bloomberg News, Google X VP Megan Smith were to be chosen as the new US CTO, her inclusion as an openly gay woman, the first to hold the post, and the application of her considerable technological acumen to working on the nation’s toughest challenges would be an important part of Park’s legacy.

Update: On September 4th, the White House confirmed that Smith would be the next US CTO and former Twitter general counsel Alex Macgillvray would be a deputy US CTO.

[PHOTO CREDIT: Pete Souza]

This post has been updated with additional links, statements and analysis.

White House e-petition system hits 15 million users, 22 million signatures and 350,000 petitions

Last week, the White House took a victory lap  for a novel event in U.S. history, when a bill that had its genesis as an online petition to the United States government filed at WhiteHouse.gov became law after the 113th Congress actually managed to passed a bill.

In a blog post explaining how cell phone locking became legal, Ezra Mechaber, deputy director of email and petitions in the White House Office of Digital Strategy, noted that this outcome “marked the very first time a We the People petition led to a legislative fix.” Mechaber also highlighted continued growth for the national e-petition platform: 15 million users, 22 million signatures and 350,000 petitions since it was launched in 2011.

WeThePeople epetition statistics

Mechaber also mentioned two other things worth highlighting: “a simplified signing process that removes the need to create an account just to sign a petition”  and a Write API that will “eventually allow people to sign petitions using new technologies, and on sites other than WhiteHouse.gov.” If and when that API goes live, I expect user growth and activity to spike again. Imagine, for instance, if people could sign petitions from within news stories or though Change.org. Enabling petition creators to have more of a relationship with signatories would also address one of the principal critiques levied against the site’s function. Professor Dave Karpf:

Launching the online petition at We The People created the conditions for a formal response from the White House.  That was a plus.  We The People provided no help in amplifying the petitions through email and social media.  That was neutral in this case, since Reddit, EFF, Public Knowledge, and others were helping to amplify instead.  But the site left the petition-creators with no residual list for follow-up actions.  That’s a huge minus.

If the petition had been launched through a different site (like Change.org), then it would have been less likely to get a formal White House response, but more likely to facilitate the follow-up actions that Khanna/Howard, Wiens and Khanifar say are vital to eventual success.

The White House has not provided a timeline for when the beta API will become public. If they respond to my questions, I’ll update this post.

White House formally launches U.S. Digital Service, publishes open source “Playbook” on Github

digital service plays

The White House officially launched a U.S. Digital Service today, promising to deliver “customer-focused government through smarter IT. The new Digital Service will be “a small team made up of our country’s brightest digital talent that will work with agencies to remove barriers to exceptional service delivery,” according to a blog post by Beth Cobert, deputy director for management at the Office of Management and Budget (OMB), U.S. chief information officer Steve VanRoekel and US chief technology officer Todd Park.

We are excited that Mikey Dickerson will serve as the Administrator of the U.S. Digital Service and Deputy Federal Chief Information Officer. Mikey was part of the team that helped fix HealthCare.gov last fall and will lead the Digital Service team on efforts to apply technology in smarter, more effective ways that improve the delivery of federal services, information, and benefits.

The Digital Service will work to find solutions to management challenges that can prevent progress in IT delivery. To do this, we will build a team of more than just a group of tech experts – Digital Service hires will have talent and expertise in a variety of disciplines, including procurement, human resources, and finance. The Digital Service team will take private and public-sector best practices and help scale them across agencies – always with a focus on the customer experience in mind. We will pilot the Digital Service with existing funds in 2014, and would scale in 2015 as outlined in the President’s FY 2015 Budget.

The USDS goes live with a Digital Services Playbook and “TechFAR,” a subsection of the guide that “highlights the flexibilities in the Federal Acquisition Regulation (FAR) that can help agencies implement ‘plays’ from the Digital Services Playbook.”

In what now appears to be de rigueur for information technology and digital government initiatives in the second term of the Obama administration, the playbook has been published on the White House account on Github, where the public is encouraged to give feedback and make suggestions upon the documents using  GitHub Issues and to propose changes to the playbook by submitting a pull request. According to the Github account, pull requests that are made and accepted before September 1, 2014 “will be incorporated into the next release of the Digital Services Playbook and the TechFAR Handbook.”

While a team of 25 folks in OMB led by former Googler Mikey Dickerson and a playbook will not prevent the next healthcare.gov debacle, there’s a lot that’s good here.

As some guy wrote in November 18, 2013: “If Obama now, finally, fully realizes how much of an issue the broken state of government IT procurement is to federal agencies fulfilling their missions in the 21st century, he’ll use the soft power of the White House to convene the smartest minds from around the country and the hard power of an executive order to create the kernel of a United States Digital Services team built around the DNA of the CFPB: digital by default, open by nature.”

This isn’t quite that – the USDS looks like more of a management consulting shop, vs the implementation and building than the Presidential Innovation Fellows and folks at 18F, but maybe, all together, they’ll add up to much more than the sum of their parts.