Sprint User Testing: Running Design Sprint Day 5

Sprint user testing on design sprint day 5: recruit five target customers, run five-act interviews, score each sprint question and decide next steps.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

Sprint user testing is the design sprint day 5 activity that gives the week its answer. Five customers who fit the target profile each spend a one-on-one session with the prototype while the rest of the team watches on a video feed. By the end of the day the team knows which sprint questions came out yes, which came out no, and what to do next. GV describes the test as the step that "makes the entire sprint worthwhile" (GV).

The format is specific. The checklist from Jake Knapp and John Zeratsky calls for all five interviews in one day, a separate interview room with one-way video to the sprint room, and an interview structure called the Five-Act Interview (Design Sprint guide). The GV page lists a Five-Act Interview video with Michael Margolis, whose research methods it credits with getting "crystal clear results in just one day." The team observes together, which the checklist summarises as "Watch together, learn together."

Five is a deliberate number. The checklist says "Five is the magic number": after five interviews, big patterns emerge. That matches Jakob Nielsen's long-standing argument for small usability studies, in which he wrote that the first study with five participants found 85% of the usability problems and recommended running several small tests instead of one large one (Nielsen Norman Group). A sprint test is usability testing in a design sprint with a twist: it scores the team's own risk questions from Monday, as well as usability.

The skill covers recruiting, the script, the interview itself, note-taking by observers, and the end-of-day verdict. It depends on the earlier days. The sprint questions from day 1 become the scorecard, and the prototype must be frozen before the first customer arrives. The Google Design Sprint method page explains how Friday closes the loop the week opened.

How It Works

Recruiting starts early in the week. The checklist asks the team to put one person in charge of recruiting, which takes one or two extra hours a day, to write a screener survey that identifies target customers without revealing who you want, and to follow up by email and phone (Design Sprint guide). Build in a spare. AJ&Smart, for example, recruits "six users: 5 + 1 extra" in case someone cannot make it (AJ&Smart).

The Five-Act Interview gives each session the same shape. Act one is a friendly welcome that puts the customer at ease. Act two is context questions, starting with small talk and moving to the topic. Act three introduces the prototype, reminding the customer that some things may not work, that you are not testing them, and asking them to think aloud. Act four is tasks and nudges: the customer figures out the prototype on their own, with simple prompts and follow-up questions. Act five is a debrief that asks the customer to summarise.

Thinking aloud is the core technique. Nielsen Norman Group defines it as asking participants to use the system "while continuously thinking out loud," and notes that the facilitator usually has to prompt people to keep talking (Nielsen Norman Group). The checklist's interviewer tips point the same way: ask open-ended questions, avoid leading yes/no questions, and let questions trail off so the customer fills the silence.

Observers turn what they see into a score. Before the first interview, draw a grid on a whiteboard with a column for each customer and a row for each question to answer, such as Monday's risks or the assumptions behind the prototype. During each interview, observers write quotes, observations and interpretations on sticky notes and mark them positive or negative. After each interview, they vote yes or no on each question for that customer, and the Decider chooses the answer for the cell (Design Sprint guide).

At the end of the day the Decider sets a single yes or no for each question on the scorecard, and each person writes down their "hot take" and proposed next steps before the Decider decides. The Remote Design Sprint Guide notes that Knapp and Zeratsky later found tracking answers to key questions in a spreadsheet faster than sticky notes on the wall (Remote Design Sprint Guide).

Step-by-Step Guide

Step 1: Recruit and confirm five customers

On Monday or Tuesday, put one person in charge of recruiting and write a screener that identifies the target customer without giving away the answer. Recruit five plus at least one backup, and schedule them across Friday with a short gap between sessions. Confirm each appointment, and remind everyone the day before, by phone where possible (Design Sprint guide). Prepare thank-you gifts for participants.

Step 2: Write the interview script

On Thursday the Interviewer writes the script following the five acts: welcome, context questions, prototype introduction, tasks, debrief. Draft context questions that reveal how the customer handles the problem today. Write tasks that walk through the storyboard without telling the customer where to click. End with debrief questions that ask them to compare the prototype with what they use now.

Step 3: Set up the rooms and the scorecard

Prepare two rooms: a small, comfortable one for the interview and the sprint room where the team watches. Set up a camera on the customer's face and, for a phone or device, a view of the screen, and stream one-way video and audio to the sprint room (Design Sprint guide). On the sprint room whiteboard, draw the scorecard grid: one column per customer, one row per sprint question. Hand out sticky notes and markers.

Step 4: Run the five-act interviews

Welcome each customer, explain you are looking for candid feedback, and ask context questions. Introduce the prototype, say that you are testing the design and not them, and ask them to think aloud (Nielsen Norman Group). During the tasks, watch and ask open questions such as "What are you looking for?" rather than explaining the screen. Close with the debrief and thank the customer.

Step 5: Take notes and score after each interview

Observers write quotes, observations and interpretations on sticky notes during each session, marking each as positive or negative. After the customer leaves, each observer votes yes or no on each sprint question for that customer. The Decider looks at the votes and records the answer in the grid. Take a quick break before the next customer arrives.

Step 6: Read the patterns across all five

When the last interview is done, look across the rows. A question answered the same way by most customers is a clear signal; a split row means the answer depends on the customer or the prototype did not test it cleanly. Look at the sticky notes behind each cell to understand why. Mark surprises that none of the sprint questions anticipated.

Step 7: Decide and record next steps

The Decider sets a single yes or no for each sprint question on the scorecard (Design Sprint guide). Each person writes a hot take and proposed next steps, then the Decider decides what happens next: move ahead, run a follow-up sprint on the weak spots, or drop the direction. Photograph the scorecard and notes, and share a short summary with stakeholders who were not in the room.

Best Practices

• Recruit people who match the target from Monday. Five interviews with the wrong customers produce clear but misleading patterns, which is why the checklist relies on a screener survey.
• Keep one Interviewer for all five sessions. The same person running the same script makes differences between customers easier to attribute to the customers.
• Let customers struggle before nudging. Nielsen Norman Group's advice for think-aloud tests is to let users do the talking (Nielsen Norman Group); a quick rescue hides the problem you came to find.
• Have the whole team watch. The checklist's "watch together, learn together" means the Decider and the builders see the same evidence at the same time.
• Score after every interview. Waiting until the end blurs sessions together and lets the last customer dominate.
• Book a backup participant. A no-show on a five-person day removes a large part of your evidence.

Common Mistakes

• Testing with colleagues or friends: Internal testers know too much and want to be kind. Recruit real target customers through a screener.
• Leading the customer: Asking "Would you use this?" or explaining how a screen works produces answers the team wants to hear. Ask open questions and let the customer figure it out.
• Spreading interviews over several days: Separate days let the team drift back to other work and weaken the shared read. Run all five in one day as the checklist recommends.
• Changing the prototype between sessions: Fixing issues after customer two makes the sessions incomparable. Freeze the prototype and note the fixes for later.
• Ending without a verdict: A list of observations with no yes or no on the sprint questions leaves the week's decision open. The Decider should score every question before the day ends.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: Google Design Sprint

Related Skills

• Building a Realistic Sprint Prototype in One Day
• Design Sprint Day 1: Map the Problem and Pick a Target
• Running a Remote Design Sprint with Distributed Teams
• Design Sprint Facilitator: How to Facilitate a Sprint

Sources

• Jake Knapp and John Zeratsky: Design Sprint guide
• GV: The Design Sprint
• Nielsen Norman Group: Why You Only Need to Test with Five Users
• Nielsen Norman Group: Thinking Aloud, the top usability tool
• AJ&Smart: What is a Design Sprint
• The Remote Design Sprint Guide

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.