Five principles to guide any government IT effort
TL;DR: Nearly three years later, the founding principles of project MyGov remain valid guideposts for any reform effort in government.
Three years ago to the day, the first class of Presidential Innovation Fellows were sworn in. Being part of the inaugural class was a lot like founding a startup: we had to define our problem space, figure out basic mechanics like where to work or how to get laptops and servers, and most importantly, had the opportunity to create our own culture around how we approached problems.
Well before we wrote our first line of code, we defined a set of guiding principles. The principles helped us lay the blueprint for how to deliver on the Project MyGov charter:
To reimagine how citizens interact with government through an experience designed around their needs rather than a confusing and fragmented bureaucracy.
Looking back three years later, many of those principles still remain valid guideposts for any reform effort in government:
Change the culture. The PIF program, 18F, USDS… half of what they deliver is code. Only half. The other half of their product, the value they provide to government, is leaving their agency partners with a better understanding of and appreciation for what modern software development looks like and to disrupt bureaucracies and challenge assumptions in the process.
Serve the people first, and the government second. Reform efforts in government often confuse stakeholders with customers. The customer, the end user of the product or service being reengineered, is always going to be the American people. It may be developers, it may be veterans, it may be retirees. Despite the intermediary steps, the customer is rarely, if ever, a government bureaucrat. Optimize accordingly.
Engineer simplicity. Citizen-centric design means reducing the cognitive burden required to use government services. It means leveraging technology to absorb the complexity of bureaucracy on behalf of the public. A user shouldn’t need to study the org chart to know where to submit a form and they definitely shouldn’t have to tell the government the same information twice, especially information it should already know.
Solve for actual needs, not perceived ones. Between interest groups, the media, and Congress it’s all too easy to be perpetually beholden to the squeakiest wheel. Data-driven decision-making can often solve for this request whack-a-mole. At the FCC, for example, we used analytics to show that lawyers and lobbyists were actually a tiny subset of visitors to
fcc.gov, and the use cases the site was optimized for shifted accordingly.
Build a platform. We’re well past government as a platform. Government is a platform. Heck, most tech. companies today are platforms (see, for example, Google, Apple, and Microsoft). If you’re not building a platform first and a site, app, or workflow second, you’re engineering from the outside in. Be lean, be modular, be decentralized. Expose APIs. Encourage reuse and collaboration through interoperability. Grow an ecosystem. Eat our own dog food.
An organization’s principles are more than mere words. They’re the underlying assumptions that constrain all decisions. In government, it’s all too easy to focus on the code, on the concrete deliverable. After all, RFPs, rarely, if ever, mention culture or customers or citizen-centricity. As the MyGov principles ask, “are [you] solving for the right thing”?
H/T @californiakara, the author of the original post, and whose Tweet let me to rediscover it.
If you enjoyed this post, you might also enjoy:
- Ten ways to make a product great
- Why open source
- 19 reasons why technologists don't want to work at your government agency
- The difference between 18F and USDS
- The three biggest challenges in government IT
- Five best practices in open source: external engagement
- 15 rules for communicating at GitHub
- Everything an open source maintainer might need to know about open source licensing
- Twelve tips for growing communities around your open source project
- Four characteristics of modern collaboration tools
- Why everything should have a URL
Ben Balter is the Director of Engineering Operations and Culture at GitHub, the world’s largest software development platform. Previously, as Chief of Staff for Security, he managed the office of the Chief Security Officer, improving overall business effectiveness of the Security organization through portfolio management, strategy, planning, culture, and values. As a Staff Technical Program manager for Enterprise and Compliance, Ben managed GitHub’s on-premises and SaaS enterprise offerings, and as the Senior Product Manager overseeing the platform’s Trust and Safety efforts, Ben shipped more than 500 features in support of community management, privacy, compliance, content moderation, product security, platform health, and open source workflows to ensure the GitHub community and platform remained safe, secure, and welcoming for all software developers. Before joining GitHub’s Product team, Ben served as GitHub’s Government Evangelist, leading the efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies for code, data, and policy development. More about the author →
This page is open source. Please help improve it.Edit