Summary
Russ, a manager at 18F, details how the Presidential Innovation Fellows program inspired the creation of 18F inside the General Services Administration to improve government technology and services through agile, user-centered, and open source approaches. He explains 18F's commitment to being federal employees working collaboratively with government agencies, emphasizing distributed and inclusive hiring across the country. Russ highlights how 18F developed a partnership playbook to manage demand and set clear expectations about their service model. Julia Elman contributed a project evaluation guide that helped align design needs with agency goals. Russ underscores the critical role of content designers in the team, noting their earned respect in government projects and their impact on plain language and accessibility. He recounts the creation and success of the US Web Design Standards, promoting adaptable, accessible, and consistent UI components to reduce cognitive load across thousands of government websites. Russ shares the example of the Federal Interagency Fourth Grade Park Pass, where Emily Barnes ensured content was written at an accessible fourth-grade reading level, helping more than 500,000 kids gain free national park access and illustrating the power of content coequal with design. He concludes with lessons learned about setting limits, creating shared language, establishing reusable patterns, and equalizing team roles as essential to removing paralysis and improving government digital experiences.
Key Insights
-
•
18F was formed by Presidential Innovation Fellows to embed agile, user-centered design within government as federal employees rather than contractors.
-
•
Distributing hiring nationwide allows 18F to find top tech talent regardless of location, enabling remote work with occasional travel.
-
•
A partnership playbook clarifies 18F’s scope, avoiding mismatched expectations and ensuring agencies understand how projects are run.
-
•
Content design is a vital and previously underrated discipline within government digital teams, proven critical for accessibility and plain language.
-
•
Julia Elman’s project evaluation guide helps identify when design work is necessary and aligns team understanding early in projects.
-
•
The US Web Design Standards promote adaptability over uniformity, prioritizing accessibility (508 and ADA compliance) while allowing agency personality.
-
•
Government websites face challenges from inconsistent design practices across thousands of agency sites, creating a confusing user experience.
-
•
Emily Barnes led content efforts on the Federal Interagency Fourth Grade Park Pass, ensuring all materials were at a fourth-grade reading level for inclusivity.
-
•
More than 500,000 fourth grade park passes were downloaded quickly, showing success in targeted, accessible government outreach.
-
•
Removing project paralysis relies on setting limits, shared design language, reusable patterns, and valuing all team roles equally.
Notable Quotes
"We’re not contractors. We all work in our government. We work with our government."
"If you are the best front end designer in the country, and you live in West River Idaho, and have internet, we should be talking."
"We created a partnership playbook so agencies know what to expect when they come to us."
"Our work is open source and public. As taxpayers, we believe you get it."
"You aren’t your user, but we are users of this system and have to make sure it works well for us to work well for others."
"20% of our design team are content designers, and that’s been an absolute game changer."
"We found that having method cards actually made people more comfortable and knowledgeable about design methods."
"There are thousands of government websites with infinitely many button styles — it adds cognitive load when moving between them."
"Our US Web Design Standards focus on easy to use, adaptable, accessible components - consistency over uniformity."
"Removing paralysis requires setting limits, shared language, reusable patterns, and equalizing all roles on the team."
Or choose a question:
More Videos
"We want teams to have autonomy and power to make pivot, shelve, and proceed decisions, not leadership dictating."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"Space has meaning in a map—if you move components around without reason, it’s no longer a map."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Bias is a tendency, feeling or opinion for or against something without reason or evidence."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"I felt on edge around Jeff and physically depleted after our interactions."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Stakeholder communication is crucial to professional strategy because without it, we run the risk of activity without impact."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Craft should evolve from making a beautiful final object to serving as a facilitative anchor in enterprise UX."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Trust is often underestimated but is critical when designers face public critique and feedback."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"If you come with a big idea, they’ll try to dial you back to the smallest iota you can test first."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Design leaders want predictable roadmaps and healthy teams, measurable against timelines and goals."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
