Skip to content
The Official 5-Day Design Sprint
  • Pages
    • The Official 5-Day Design Sprint
    • Set the stage
      • Sprint basics
      • Big challenge
      • Sprint team
      • Email Summary
    • Monday: Map
      • 1. Introductions
      • 2. Explain the sprint
      • 3. Long-term goal
      • 4. Sprint questions
      • 5. Map
      • 6. Lunch
      • 7. Ask the experts
      • 8. Target
    • Tuesday: Sketch
      • 1. Lightning demos
      • 2. Divide or swarm
      • 3. Sketch
        • Example
        • All Crazy 8's
        • All Solutions
      • 4. Begin recruiting
    • Wednesday: Decide
      • 1. Sticky decision
      • 2. Rumble
      • 3. Storyboard
    • Thursday: Prototype
      • 1. Pick the right tools
      • 2. Divide and conquer
      • 3. Build the prototype
      • 4. Do a trial run
      • 5. Prepare for tomorrow
    • Friday: Test
      • 1. Interviews
      • 2. Take Notes
      • icon picker
        3. Make a plan
The Official 5-Day Design Sprint
/
/
3. Make a plan
Share
Explore

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
⁠
⁠
Who
On Track?
The Headline
Next steps
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
Label
Description
✅ Yes
Overall a success, but with a few parts you need to refine.
❌ No
Customers reacted poorly to the prototype. But hey, at least you know now and didn’t spend weeks/months building it for real.
? 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.
Allocated time
Timer
Time Left
00
3
Start
-
There are no rows in this table
⁠
Who
On Track?
The Headline
Next steps
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.
⁠



3. Next steps

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

Assignments
Task
Who
Date
Done?
Identify basic technical needs from prototype
Tue, Nov 2
Consolidate notes from test
Thu, Nov 4
Heat map notes from
1. Sticky decision
⁠
⁠
Fri, Nov 5
Sketch based on notes
Tue, Nov 9
Update prototype based on sketches
Thu, Nov 11
Test again with new set of customers
Fri, Nov 12
There are no rows in this table
⁠

⁠
Back to:
The Official 5-Day Design Sprint
⁠
⁠
Gallery
 
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.