An open letter to government CIOs
TL;DR: Government CIOs should seek to build systems in a lean, iterative, decentralized, and open way
Hey there government CIOs. I’ve noticed you’ve been getting a bit of a bad rap recently. And I have to say, with all the stories of multi-million dollar sites going around, I’m not sure that I can fault your critics. But don’t get down on yourself, at least not yet. You’re still in great shape. You’ve got ample resources; you’ve got smart, well-intentioned people working for you; and you’ve got more low-hanging fruit than most private-sector CIOs can ever dream of.
The problem’s not budgetary, legal, or policy constraints, although I’m those sure don’t help much. The problem’s more a matter of taste, really. It’s a matter of style. A matter of lacking a particular finesse in execution. It’s a matter of doing things right from day one. And we’re here to assure you that it’s really not that hard if you put your mind to it. Come to think of it, it’s actually a matter of doing less, not more. You should be thinking smaller, not bigger, setting your sights lower, not higher, and away from organization-wide change in favor of quick, tangible wins that we can all share.
But hey, the good news is that you’re not in it alone. We (the internet) are here to help. We’ve been here before, and we’re still here to tell the story. Just follow this simple Style Guide for building new systems going forward, and you’ll be shipping quality code in no time:
If there’s a less heavyweight solution, and you’re not using it, you’ve over-engineered things. Look to existing tools (think open source), services (think APIs), and practices (think shared standards). Simpler applications are easier to scale, easier to maintain, and have fewer components that can break. Prefer JSON to XML, REST to SOAP, and static to dynamic. Fear complexity.
If you are not embarrassed by the first version of your product, you’ve launched too late. It doesn’t need to be perfect or complete. Publicly ship 0.1, not 1.0. Start small and ramp up to where you want things to be. Watch how customers receive things and adapt accordingly. Be transparent, manage expectations. Let your vision evolve.
Avoid single points of failure, both in systems and in people. Foster communities. Push decisions to the edge. Put your faith in the crowd. Don’t bake in locks. Avoid blockers. Automate wherever possible. Eliminate all humans.
Barriers to the free-flow of information just add friction and more often than not, you just end up shooting yourself in the foot. Make open the default. Open standards, open formats, open systems. Expose process. Prefer social and cultural norms to technical constraints. Don’t lock it down unless you absolutely have to. Trust people.
And that’s about it. You’ll instantly be on the path to building apps like the cool kids in the private sector. Lean, iterative, decentralized, open. Hey, the technology’s the easy part. It’s the culture you have to worry about.
- The people who build the internet
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
- Twelve tips for growing communities around your open source project
- Five best practices in open source: external engagement
- 15 rules for communicating at GitHub
- Four characteristics of modern collaboration tools
- The three biggest challenges in government IT
- Eight things I wish I knew my first week at GitHub
- The difference between 18F and USDS
- Ten Things You Learn As A Presidential Innovation Fellow
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 →