First Time in Government

“The President of the United States is going to call you in three hours to offer you the job, so I need to know in two whether you will say yes because we do not surprise the President.” That’s what Todd Park, U.S. Chief Technology Officer (CTO), said to me in August of 2014 as our family was about to head back to San Francisco for the new school year.

Todd Park, Assistant to the President and Chief Technology Officer
shows President Obama information on a tablet April 15, 2013.
Official White House Photo by Pete Souz

In those two hours, I tried to figure out if I could really make a significant positive impact in the job the President would offer me as Deputy U.S. CTO. And, if so, whether that was worth moving our family.  The ability to make a positive impact is generally my north star when trying to make job decisions, but time and again, when I am looking back on whether taking a job was the right decision, the quality of the team I got to work with is always most important. Now that I’ve had some time to reflect on my time in government, and the entire Obama team has moved on from team CTO, I know that this time was no different. While I am extremely grateful for the impact of the work I was privileged to do, I am most happy about my time in government because of the the people I got to do it with.

The Eisenhower Executive Office Building, home of the
U.S. CTO, pictured c 1907, then the State, War & Navy Building
Gall, George, Washington: The Capital of the Nation (1907).
Digitized by The Internet Archive from the Library of Congress

The impact of government work was amazing. Our purpose was clear: help make life better for and with the American people. Under President Obama, Team CTO had significant impact working together along with many others in our home at the Office of Science and Technology Policy (OSTP), elsewhere in the White House, and across the Federal Government. We supported the work done by previous CTO teams to bring tech capacity to government in the form of the Presidential Innovation Fellows, 18F, U.S. Digital Service, and revamped Office of Digital Strategy. We brought more data science and data scientists into government through the creation of the U.S. Chief Data Scientist team and role, and creating a data science cabinet. We expanded data collaborations for solutions in justice, jobs, housing, education, and more, while continuing to get more government data out to the public. The Open Government Partnership (OGP) continued to thrive and grow and we shepherded the U.S. Open Government National Action Plans while teaming up with the National Security Council and State Department to help lead the U.S. OGP. With support from the Chief of Staff, we created a new tool for tech policy making called the Tech Policy Task Force -- which added “TQ” to many policy tables, formulated a federal source code policy, moved the government forward on artificial intelligence and uncrewed aerial vehicles, accelerated open educational resources, highlighted the opportunities and challenges of big data and algorithmic decision making, and worked with the Departments of Education, Transportation, Commerce, State, Homeland Security, Justice, and others to help regulations get out of the way of innovation while protecting people’s rights and lives. We pushed for greater recognition of all American talent, including women and underrepresented minorities in STEM; catalyzing for improvements in the portrayal of STEM people in media; expanding inclusive opportunity in computer science education; ensuring outreach for jobs in innovative industries in hiring programs, such as TechHire; increasing Internet connectivity in the U.S. and around the world; championing innovative local community solutions; pushing through more diversity and inclusion in the Federal government workforce; and expanding best practices in organizations and companies in diversity, equity, and inclusion, including an implementation action grid, the Tech Inclusion Pledge, and expanded inclusive venture funding.  And, lots more. Even reading the list brings a tired smile to my face.

President Obama writes his first line of code and celebrates
with the middle school student who helped teach him, Dec. 8 2014.
Official White House Photo by Pete Souza

So, while there was no shortage of impact, I still would say that it was the people that were the most important reason why I was so glad that I had the opportunity to work government. The diversity of people in the White House and at agencies was a huge difference from Silicon Valley. That diversity was expressed in terms of the traditional lines of socio-economic, ethnicity, race, color, religion, age, disability status, gender identity, sexual orientation, and far more balanced gender representation, but also in terms of point of view, educational, geographic origin, and career background. Sometimes, I was among others like me but more frequently I was unusual along a number of dimensions such as my lack of long federal service, my lack of military service, my tech background, etc. I came away extremely impressed with the level of experience, intellect, and passion that the Obama White House was able to attract. There were people who you later discovered were Rhodes Scholars, or Supreme Court clerks, or had beaten a Scrabble world champion over the weekend. I had expected both the diversity and excellence, but it is one thing to expect something and quite another to live it for two-plus years.

President Obama talks with U.S. CTO Megan Smith, and
OSTP Director Dr. John Holdren, Oct. 8, 2014.
Official White House Photo by Pete Souza

Team CTO under U.S. CTO Megan Smith was also outstanding. I had the privilege of working with a number of people that I have admired and wanted to work for for years. I also got to meet and work with a bunch of folks that I might never have otherwise met. Over my time there, the U.S. CTO team while I was there included at different times: Puneet Ahira, Seth Andrew, Rob Bacchus, Jake Brewer, Marvin Carr, Jimmy Catania, Colleen Chien, Evan Cooke, R. David Edelman, Ed Felten, Anjali Fernandes, Brian Forde, Brianna Fugate, Dipayan Ghosh, Vivian Graubard, Renee Gregory, Dan Hammer, Natalie Evans Harris, Read Holman, Kristen Honey, Mina Hsiang, Kelly Jin, Terah Lyons, Matthew McAllister, Dawn Mielke, Lynn Overmann, Ryan Panchadsaram, DJ Patil, Tom Power, Laura Weidman Powers, Jason Schultz, Nick Sinai, Lauren Smith, Ashkan Soltani, Suhas Subramanyam, Emily Tavoulareas, Maya Uppaluru, Aden Van Noppen, Nancy Weiss, Claudia Williams, Charles Worthington, Cori Zarek, and, of course, the wonderful Megan Smith herself.

Yowza.

Some of the wonderful folks that made up team CTO,
Jan. 14, 2017.

That combination of a top-notch team amid a diverse broader group of excellent folks from top to bottom at OSTP, the broader White House and across the Government, made going into work both a joy and a challenging learning experience every day. I felt like I grew a ton, learned a lot about how the U.S. government functions, and picked up some really interesting management and leadership lessons from the people I got to work with. I came home mentally worn out but almost always smiling. I also made a bunch of new friends.

President Obama talks with Girl Scout White House Science
Fair participants who had designed a Lego page turner to help
people read books who may not otherwise be able, Mar. 23 2015.
Official White House Photo by Pete Souza

Now that I have been out of work for a few months, I am thankful for the opportunity to make a positive impact but I am certain that I made the right choice that August because of the amazing people I got to work with. I am still fired up that I had the privilege to serve with each and every one of them, and ready to go and work with them again!

President Obama, listens during a technology 

strategy discussion, Oct. 8, 2014.

Official White House Photo by Pete Souza

Councils and Policy

A bunch of friends in Silicon Valley have asked some version of “what was surprising to you in government?” or “what did you learn about government?” This is the first of a series of posts answering those questions.

Most policy within the Obama White House was decided through policy councils, and their Principals, Deputies, and Interagency Committees. These are both specific groups of people (similar to Boards of Directors at companies) and also can be departments that are staffed within the White House (similar to business units within companies). What each council decides and the membership of the various councils are important determinants of the quality of decisions and what policy can be advanced. This post gives some background about a non-exhaustive list of policy councils, their jurisdiction, and their membership with a focus on those relevant to tech policy.

One important note is that the Obama administration found it useful to ensure that tech and scientific expertise had its own council-like apparatus and had seats at each of the other policy making tables so that policy decisions could be informed by the latest technical and scientific innovations. The Trump administration has signaled that it also believes that tech is important to effective governance and now is the time that administrations typically begin to formalize how they make decisions as well as the jurisdiction, membership, and attendees of their various councils (indeed the President Trump just did so for the National Security Council -- see this earlier post for more on the changes and why they are bad). Inside and outside of the administration it is important to understand these powerful policy levers and structure them to be most effective. Today, given the importance of technology and science to policymaking of all types, that means including technical and scientific expertise at each of these tables.

National Security Council

President Truman established the National Security Council (NSC) in 1947, and it is enshrined in law as part of the National Security chapter of Title 50. Its function is to:

“advise the President with respect to the integration of domestic, foreign, and military policies relating to the national security so as to enable the military services and the other departments and agencies of the Government to cooperate more effectively in matters involving the national security.”

It is led by the President of the United States or their delegate and must include the Vice President and Secretaries of State, Defense, and Energy but it can include others either at all meetings or only when germane. President Obama gave direction as to its jurisdiction, decision making processes, and membership in his first Presidential Policy Directive (PPD-1) published less than a month after his inauguration. Reading PPD-1 gives a good sense of how policy councils operate, with principals, deputies, and interagency committees all working to produce policy decisions.

NSC was the most important and largest of the councils during my time in government. Its staff were experts at running effective process and went on to become important members of the Office of the Chief of Staff, including the Chief of Staff, Denis McDonough; his advisor and Deputy Assistant to the President, Natalie Quillian; and the Deputy Chief of Staff for Implementation and Assistant to the President, Kristie Canegallo.  Getting a seat for an NSC decision meeting on an important topic could be difficult as NSC staff tried to keep the decision making tight. However, being there was extremely important and, depending on the decision, getting tech expertise in the room could be the difference between making one decision and another.

President Obama convenes the NSC in the White House Situation Room
Official White House Photograph by Pete Souza

National Economic Council

The National Economic Council (NEC) was created by President Clinton and enshrined by an Executive Order in 1993. Its remit is to:

“(1) to coordinate the economic policy-making process with respect to domestic and international economic issues; (2) to coordinate economic policy advice to the President; (3) to ensure that economic policy decisions and programs are consistent with the President’s stated goals, and to ensure that those goals are being effectively pursued; and (4) to monitor implementation of the President’s economic policy agenda”

It is led by the President of the United States or their delegate and includes the Vice President a wide range of agency heads, leads of White House components, and Assistants to the President. President Obama expanded its membership to add more members, including the U.S. Chief Technology Officer.

Domestic Policy Council

The Domestic Policy Council (DPC) existed as a counterpart to the NSC focused on domestic policy generally until the NEC was formed to deal with economic issues, which created the narrower modern DPC through Executive Order. Its functions are:

“(1) to coordinate the domestic policy-making process; (2) to coordinate domestic policy advice to the President; (3) to ensure that domestic policy decisions and programs are consistent with the President’s stated goals, and to ensure that those goals are being effectively pursued; and (4) to monitor implementation of the President’s domestic policy agenda.”

It is led by the President of the United States or their delegate and includes the Vice President a wide range of agency heads, leads of White House components, and Assistants to the President. President Obama also modernized the makeup of the DPC, including adding the U.S. Chief Technology Officer to its membership.

National Economic Council and Domestic Policy Council planning meeting in the Roosevelt Room
Official White House Photo by Pete Souza

National Science and Technology Council

The National Science and Technology Council (NSTC) was created by President Clinton in 1993 through Executive Order as a policymaking body for Science and Technology policy. Its functions are:

(1) to coordinate the science and technology policymaking process; (2) to ensure science and technology policy decisions and programs are consistent with the President’s stated goals; (3) to help integrate the President’s science and technology policy agenda across the Federal Government; (4) to ensure science and technology are considered in development and implementation of Federal policies and programs; and (5) to further international cooperation in science and technology.

It is led by the President of the United States or their delegate and includes the Vice President a wide range of agency heads, leads of White House components, and Assistants to the President. President Bush added the Secretary of Homeland Security. NSTC was active during the Obama administration under the leadership of the President’s Science Advisor, Dr. John Holdren.

Tech Policy Task Force

The Tech Policy Task Force (TPTF) is a Executive Office of the President (EOP) policymaking body formed during the Obama Administration to develop tech policy and advise other policy councils. It is chaired by the U.S. Chief Technology Officer and its membership includes the leadership of each of the technology components within the EOP (e.g., the Federal Chief Information Officer, the U.S. Digital Service Administrator, etc.) as well as representatives from each of the other policy councils. In contrast to other councils, more than half of TPTF membership is drawn from tech components.

TPTF’s work in the Obama Administration included public policy that is tech focused, such as Artificial Intelligence policy, and policy in which tech plays a role, such as consumer privacy or national security declassification. TPTF has been used to create tech-related policy, such as the Federal Source Code Policy; to enable and engage in a policy discussion in another policy council; to advise and assist with agency efforts, such as international connectivity with the State

Department; and to answer questions raised by the President’s senior advisors and other EOP

leadership, such as with respect to cybersecurity and the Cybersecurity National Action Plan.

TPTF, in turn, has been leveraged in the policymaking efforts of other policy councils, such as

the NSC, to enhance their work with tech expertise.

For More Information

Abramson, Mark; Wagner, Martin; Breul, Jonathan; Kamensky, John; and Chenok, Daniel editors, Getting It Done A Guide for Government Executives, Revised Edition, Rowan & Littlefield (2013) (See Chapter 8 for a detailed description of policy councils).

Sargent, John & Shea, Dana, Office of Science and Technology Policy (OSTP): History and Overview, Congressional Research Service (2016) (providing an overview of the Office of Science and Technology Policy, NSTC, and the President’s Council of Advisors in Science and Technology).

N.B. This post was mostly written before President Trump’s NSC organizing Memorandum last Saturday which caused me to write a summary of the bad changes he made to the NSC that duplicates some language from this one.

Update 1/31/17: This post was updated to make the relationship between Councils and Principals, Deputies, and Interagency Committees more clear.