recommended reading

How to Hack the System to Change Government

Jennifer Pahlka

Jennifer Pahlka // Wikimedia Commons

Jennifer Pahlka, the founder of the Code for America initiative who is now working for the Obama administration as deputy chief technology officer, has been in government for 37 days -- 51 if you count weekends.

Pahlka is counting the days, because she has given herself a year to make a difference in pushing government into the 21st century from a technology perspective. At the Next Generation of Government Summit in Washington on Thursday, Pahlka shared the lessons of her first weeks in government and as head of Code for America, where she worked on civic-oriented data projects at the local government level.

“I know people say that in government, the easy things are hard, and the hard things are impossible,” Pahlka said. “Really? Was it easy to put a man on the moon?”

Pahlka works closely with the Presidential Innovation Fellows, a group of innovators and entrepreneurs who do short-term stints in government to work on specific projects. The group, she said, represents a collective “hack on the system.”

One member of the new class of fellows, Robert L. Read, managed in 27 days to develop a data visualization tool showing prices paid for a particular type of laptop across government.  “I know people -- not through their own fault -- who were still struggling to get their email set up on their 27th day,” Pahlka said.

The idea of the fellows program is to give participants as much freedom as possible to navigate through the maze of federal rules and regulations that can stand in the way of implanting new tools and approaches. “Many people in government wish they had a longer leash to do what they do,” Pahlka said.  The secret to success, she said, is thinking of government as if it were a person:  “You can’t change it unless you love it.”

“Respect the people,” she added, “but change the system.” That often requires questioning whether roadblocks are actually unavoidable. “If someone says you can’t do something, it may not be the law or regulations that prevent you,” Pahlka said. “It may just be memos written around them.”

Much of her initial work has focused on President Obama’s second-term management agenda, which is centered on the idea of leveraging technology to improve the performance of government.

“It’s been quite a wild ride,” Pahlka said, involving “an enormous amount of work by an enormous amount of people.” Still, she added, “these are the things I just absolutely geek over.”

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.


When you download a report, your information may be shared with the underwriters of that document.