Design Sprint Case Study: How NIAID used a 5-Day Sprint to design, prototype, and test a solution before writing a single line of code.

Gathering stakeholder and user input is critical before devoting time and resources toward developing your next project. Too often, that input can get de-valued when operating on a short timeline, or worse, can go on indefinitely, delaying start of the build or taking up developer time creating solutions                that may not resonate with users.

The Design Sprint, developed at Google Ventures to reduce risk before bringing investment prospects to market, was designed to compress ideation, prototyping, and user testing into a single week:

Day 1: Map out the problem and pick an important place to focus

Day 2: Sketch competing solutions

Day 3: Make difficult decisions to turn your ideas into testable solutions

Day 4: Create a high-fidelity prototype

Day 5: Test the prototype with actual users

At NIH’s National Institute of Allergy and Infectious Diseases (NIAID), our team set out to solve some of our biggest design challenges and determine a direction for the future of digital solutions at the institute by using the methodology of the Design Sprint infrastructure.

In this session, we will:

  • Walk you through the detailed steps of the Design Sprint, hour-by-hour and day-by-day
  • Discuss the planning and logistics that preceded our Sprint, including locating space and materials and selecting a team
  • Review some of the unexpected challenges
  • Highlight successes and go over learning opportunities

Learn whether a Design Sprint is a valuable tool for your next project and get a kick-start on putting one together for your team.

Experience Level
Session Track