The 18F Methods are a collection of tools that describe how our teams put human-centered design into practice. We’ve gathered them here and created simplified instructions to help other organizations and federal offices adopt human-centered design into their own projects. These cards are focused on design in the context of digital services, but can be adapted to non-technical design projects as well.
The basics of human-centered design
Human-centered design, also referred to as “user-centered design,” is a methodology that incorporates feedback from the people for whom you are designing throughout the design process. The goal of human-centered design is to end up with a solution that is tailored to meet people’s needs, with little wasted effort and reduced risk. To achieve this goal, design teams at 18F talk with and observe real users to understand their needs, context, and challenges, come up with design concepts that might address these challenges, and then test them with real users. Learn more about the benefits and techniques of human-centered design.
Using the 18F Methods
The 18F Methods are broken up into the four broad design phases your team is likely to go through during a project. While some cards refer to other methods, you may use them independently. You do not need to use all the cards in a section or complete certain tasks before moving on to others. Take whatever cards are most useful to your team and incorporate more tools as you’re ready.
We’ve included additional guidance for using these methods in government research, specifically around the Paperwork Reduction Act (PRA). We’re only able to include brief guidance on the PRA, and federal workers should check with their agency counsel for additional guidance. You should also read the cards in the fundamentals section for more background on conducting design research as a government employee.
Go behind the scenes
As with all of 18F’s products, the 18F Methods are completely open source. You are free to copy, share, or reuse them as you wish. We also welcome input from the public, whether it’s correcting a typo or suggesting a new method to include. You can see our guidelines for contributing on GitHub.