-
Notifications
You must be signed in to change notification settings - Fork 6
What you need to know about doing design and research in the federal government
The biggest difference about being a design or research practitioner in the federal government is that best practices from the private sector are no longer optional, but often required by law. Below are the most common areas you'll need to learn about.
The federal government is accountable for making all of its digital products conform with Section 508 of the Rehabilitation Act, which means everything we make (or buy) needs to be accessible to all users, regardless of their abilities or disabilities. This usually means making sure our products can be used with screen readers and alternate input devices, and that they’re logically easy to follow. Here are a few of the many available resources around accessibility practices:
The federal government goes to great lengths to ensure that government agencies and services aren’t creating barriers for people to access information, and that information is protected whenever it is solicited. The law that most impacts government designers’ day-to-day work is the Paperwork Reduction Act of 1995 (PRA). It's worth investing the time to get to know this law and its nuances enough to be able to confidently clear up any misconceptions you may encounter related to its implications on user research in government. In short:
The PRA is a law designed to “maximize the practical utility of and public benefit from information collected by or for the Federal Government,” specifically to:
- Reduce burden on the public and prevent the Federal government from collecting redundant information or information that they don’t actually need to provide a service,
- Make sure that the way the Federal government is collecting information to make policy is designed so that the resulting information can be used to produce meaningful, accurate statistics (think census), and,
- Give the public a chance to weigh in on how the government is collecting information.
TL;DR PRA = The federal government can’t make you fill out bad forms all willy nilly, and you get to weigh in.
In other words, the PRA is actually awesome.
— User Research Is Not Illegal, Uncle Sam, by Erie Meyer
Read this blog post in its entirely for a plain-language explainer on some of the most common misconceptions around the PRA and conducting research in government. It's written by one of the founding members of the U.S. Digital Service
The following are a few authoritative resources that provide evidence for and further explanation of the PRA exceptions and flexibilities that are relevant to the type of user research we do.
These cards describe many of the methods and tools our teams use to put human-centered design into practice. They were created to benefit our organization, our federal colleagues, and the public. These cards ensure our values are well documented throughout our organization, and they serve to help instruct future hires on how we work. Also, they are open to any and all organizations - and our federal partners - to help employ human-centered design on their own projects.
We can definitively say that GSA and OMB attorneys reviewed these cards before we published them publicly.
One method card in particular is the most directly applicable (but please review them all; they're great!) - Stakeholder and user interviews. The government research guidance in the lower right hand corner of the card is one of the parts that received the most attention and vetting from legal counsels.
No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3.
B. Paperwork Reduction Act Definition of Information 5 CFR 1320.3(h)3
This is the CFR citation from the Stakeholder and user interviews method card. The language in this section in and of itself, and out of context, is a little wonky, but it's basically a specific sub-definition of "information" as it's applied to PRA. Emphasis ours.
(h) Information means any statement or estimate of fact or opinion, regardless of form or format, whether in numerical, graphic, or narrative form, and whether oral or maintained on paper, electronic or other media. “Information” does not generally include items in the following categories; however, OMB may determine that any specific item constitutes “information”:
(3) Facts or opinions obtained through direct observation by an employee or agent of the sponsoring agency or through nonstandardized oral communication in connection with such direct observations;
This essentially says that non-standardized conversations (e.g. any sort of 1:1 interview, contextual inquiry or usability test based on a loose conversation guide) are exempt from the rules of PRA.
The language in this OIRA memo is another example of a favorable interpretation of 5 CFR 1320.3(h)3. Please see the following in the last page of the memo:
Thus, when the sponsoring agency merely observes a user interacting with a digital services tool or product and at most engages in nonstandardized oral communications with the user, the facts or opinions the sponsoring agency obtains are not subject to the PRA.
D. M-17-06: “Policies for Federal Agency Public Websites and Digital Services”
This was an update to the policies surrounding public websites and digital services for federal agencies that was issued in Nov 2016, which is worth a read in general.
This was a 2010 memo that provides guidance on how PRA relates to social media. Much of the content of this memo has implications on our approach to recruiting user research participants.
In short, you are free to use a recruiting screener to recruit participants directly from your site, or from social media, but certain rules and restrictions apply. PRA interpretations vary by agency, so be sure to make friends with DOI’s PRA officer.
Designers are responsible for honoring people’s opinions and choices, only blocking actions that are obviously going to harm others. We make sure that anyone participating in our research is doing so of their own free will, and that they have enough information to make that decision responsibly. Here are some guides and templates to help you do the same:
- 18F Handbook: Getting informed consent
- Sample participant agreement from the 18F Method Cards
Designers have an obligation to respect and protect privacy. People will not honestly participate in design processes, nor make use of products and services, they do not trust. Here are some guides and tools to help you manage PII responsibly in your design work:
- Problem statement
- Product vision
- User scenarios
- What we're not trying to do
- Product risks
- Prioritization scale
- Technical overview
- Contributing to code
- Creating a new branch
- How to prepare and review PRs
- Releasing changes
- Database change management
- Tech Solutions
- Data overview
- How to upload monthly data
- How to upload OGOR-B Data
- Troubleshooting for specific datasets
- Goals and metrics
- Analytics
- DAP-GA4 templates & instructions
- DAP-UA templates & instructions
- User research plans & findings
- Joining the team
- Onboarding checklist
- Working as a distributed team
- Planning and organizing our work
- Sample retro doc
- Human centered design process
- User research study process
- Design Standards
- Usability testing process
- User research participant guide
- User research agreement
- Observing user research
- Design and research in the federal government
- Shaping process
- Research wiki
- Data catalog
- Problem statement (2016)
- Hypotheses (2016)
- Outcomes workshop (2017)
- Transition goals (2018)
- Product management training (2018)
- Information architecture
- NRRD-flavored Markdown (Jekyll site)
For information about our other website see our ONRR.gov wiki.