The Official 5-Day Design Sprint
Share
Explore
Friday: Test

3. Make a plan

After looking back, it's usually easy to figure out the next step.
Maybe the best part about a sprint is that you can’t lose. If you test your prototype with customers, you’ll win the best prize of all—the chance to learn, in just five days, whether you’re on the right track with your ideas. The results don’t follow a neat template. You can have efficient failures that are good news, flawed successes that need more work, and many other outcomes.
Clear examples
1. Hot takes: How do you feel about the sprint?
After your last customer interview, have each teammate submit their sentiment on the sprint.
Add my hot take
Search
Who
On Track?
The Headline
Next steps
Who
On Track?
The Headline
Next steps
1
Polly Rose
✅ Yes
Showing predictions clearly and being able to dig into data to answer questions is what brings most value.
Iterate on the UI with a focus on trends, action history, and prediction detail.
Put reporting on back burner.
No results from filter
Sprint outcomes
Search
Label
Description
Label
Description
1
✅ Yes
Overall a success, but with a few parts you need to refine.
2
❌ No
Customers reacted poorly to the prototype. But hey, at least you know now and didn’t spend weeks/months building it for real.
3
? Maybe
We’re not sure. We might need to run another test that’s better suited to answering our sprint questions.
There are no rows in this table


2. Review all hot takes
Expand the table below and review the sentiments one by one as a group. Give each person 3 minutes to share.
Search
Allocated time
Timer
Time Left
Allocated time
Timer
Time Left
1
00
3
Start
-
There are no rows in this table
3
Sum
Search
Who
On Track?
The Headline
Next steps
Who
On Track?
The Headline
Next steps
Polly Rose
✅ Yes
Showing predictions clearly and being able to dig into data to answer questions is what brings most value.
Iterate on the UI with a focus on trends, action history, and prediction detail.
Put reporting on back burner.
James Booth
Joel Davis


3. Next steps
What’s the plan for next week? The
@Decider
summarizes everything heard above and documents next steps + below.
Take notes here...

Assignments
0
Task
Who
Date
Done?
Task
Who
Date
Done?
1
Identify basic technical needs from prototype
Polly Rose
Tue, Nov 2
2
Consolidate notes from test
Felix Marlin
Thu, Nov 4
3
Heat map notes from
Adam Davis
Fri, Nov 5
4
Sketch based on notes
MM
Maria Marquis
Tue, Nov 9
5
Update prototype based on sketches
Mary Jones
Thu, Nov 11
6
Test again with new set of customers
Lola Tseudonym
Fri, Nov 12
There are no rows in this table

Share
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.