Pages
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
Who
On Track?
The Headline
Next steps
✅ Yes
Showing predictions clearly and being able to dig into data to answer questions is what brings most value.
No results from filter
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
3Start
-
There are no rows in this table
3
Sum
Who
On Track?
The Headline
Next steps
✅ Yes
Showing predictions clearly and being able to dig into data to answer questions is what brings most value.
3. Next steps
What’s the plan for next week? The summarizes everything heard above and documents next steps + below.
@Decider
Assignments
Task
Who
Date
Done?
Identify basic technical needs from prototype
Tue, Nov 2
Consolidate notes from test
Thu, Nov 4
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
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.