Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Research + Discovery introduction

The Research + Discovery phase is not about solutions. It’s about uncovering problems. Before you start designing or building a service, you need to find out who the potential users are and what problems your service could solve for them.

What is the Research + Discovery phase?

It’s tempting to start brainstorming solutions right away based on your understanding of your project. Doing that leads to a solution-focused design process in which your team’s primary question is: How do we build the solution?

Instead focus on a user-centered design process in which your team’s primary questions are: Who are the potential users of my service, and how can we design a service that meets their needs?

Your goal in the Research + Discovery phase is to learn about real users and identify the problem(s) your service could solve for them. The best way to do this is to talk to real users. Go out and find people who will be using the service. Talk to them, observe them, and learn what they need and want.


Planning

  • Start the project by putting a time constraint on your Research and Discovery work. Plan to spend
    • 2 to 4 weeks for a new feature
    • 4 to 8 weeks for a new service
  • Schedule the Research and Discovery Checkpoint at least a week in advance.

Resources and help



< Onboard Team
Research + Discovery activities >