Design Sprint Checklist
Run a 5-day Google Ventures style Design Sprint with a 30-task checklist, day notes, deliverables and a progress bar, then export the report.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Design Sprint Checklist?
The Design Sprint Checklist turns the five-day sprint into 30 tickable tasks, six per day, under the headings Understand, Ideate, Decide, Prototype and Test. Each day lists its expected deliverables (for example HMW questions on day one, a storyboard on day three, user test recordings on day five) and has a notes box for decisions and insights.
A progress bar at the top shows the share of all 30 tasks you have ticked, and each day's tab gets a green dot once its six tasks are done. The Design Sprint Summary underneath shows tasks completed and notes per day, and the Text, Image and PDF buttons export it for the team or the Decider.
Progress and notes are saved in your browser under the key design-sprint, so a facilitator can keep the checklist open all week. It does not run timers, host a shared board or record interviews; use it alongside your whiteboard or Miro board.
- 30 tasks across five days with checkboxes
- Expected deliverables listed for each day
- Per-day notes saved in your browser
- Overall progress bar and per-day completion markers
- Text, Image and PDF export of the sprint summary
Updated
How to use the Design Sprint Checklist
- Start on the Understand tab and tick tasks as the team completes them: long-term goal, problem map, expert interviews, HMW questions.
- Write the day's key decisions in Day Notes & Insights before you close the session.
- Move through the days with Next Day and Previous Day, or click a tab directly.
- Watch the progress bar and the green dot on each finished day.
- Review the Design Sprint Summary and export it with the Text, Image or PDF button at the bottom.
Worked example
Reading the progress bar mid-week
Input
Understand: 6 of 6 ticked Ideate: 6 of 6 ticked Decide: 3 of 6 ticked
Output
15 of 30 tasks, progress bar at 50%
Progress is ticked tasks divided by all 30 tasks, so halfway through Wednesday you are at 50%. The Load Sample button shows a lighter state: 2 tasks on Understand and 1 on Ideate, which is 3 of 30, or 10%.
Background and insight
The Design Sprint was developed by Jake Knapp at Google and refined at Google Ventures, where he and John Zeratsky ran it with portfolio companies. The 2016 book Sprint, by Knapp, Zeratsky and Braden Kowitz, laid it out as a Monday to Friday schedule: map the problem and pick a target, sketch competing solutions, decide on the best and storyboard it, build a realistic prototype, and test it with five customers.
The five-customer rule is borrowed from usability research. Jakob Nielsen's work on small-sample testing showed that around five users surface most of the serious usability problems in a design, and the sprint book applies the same logic: by the fifth Friday interview, the patterns are usually obvious. The tool's Test day starts with "Conduct 5 user interviews" for that reason.
The day names here (Understand, Ideate, Decide, Prototype, Test) follow the older Google Ventures naming rather than the book's Map, Sketch, Decide, Prototype, Test, but the work is the same. Some tasks, such as Crazy 8s, come from the four-step sketch the book describes for Tuesday, and Rumble is the book's term for prototyping two competing ideas side by side.
Common use cases
Facilitating a sprint week
The facilitator keeps the checklist open on a laptop and ticks tasks so nobody skips the steps that make Friday's test useful.
Remote or async sprints
Spread the 30 tasks over two weeks and use day notes as the written record for people in other time zones.
Teaching the method
New facilitators see what each day must produce before they run their first sprint.
Sprint retrospective
Export the summary to compare what was planned against what the team actually did each day.
Tips and limitations
- Name a Decider before Monday. The sprint stalls on Wednesday without one person who can make the final call.
- Recruit Friday's five customers on Monday. Recruiting is the task teams most often leave too late.
- Build a facade, not a product. Thursday's prototype only needs to look real for the path the interviews cover.
- Load Sample replaces your saved progress and notes, so export first if you have real data.
- Notes are plain text; paste links to your board, prototype and recordings so the export points to the evidence.
Sources and further reading
- The Design Sprint, GV. Google Ventures' own description of the five-day process
- Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, Character. Knapp, Zeratsky and Kowitz's 2016 book
- Why You Only Need to Test with 5 Users, Nielsen Norman Group. Jakob Nielsen on the five-user rule behind Friday's interviews
Frequently asked questions
What happens on each day of a design sprint?
Day one maps the problem and picks a target, day two sketches competing solutions, day three decides and storyboards the winner, day four builds a realistic prototype, and day five tests it with five customers. This checklist names the days Understand, Ideate, Decide, Prototype and Test.
Who created the Google Ventures design sprint?
Jake Knapp developed it at Google and refined it at Google Ventures with John Zeratsky and Braden Kowitz. The three described the process in the 2016 book Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days.
Why does a design sprint test with only five users?
Five interviews usually reveal the main patterns. Usability research by Jakob Nielsen found that around five participants uncover most serious problems in a design, and testing more people in the same round adds little new. Run another round after you fix what you learned.
How is design sprint progress calculated here?
Progress is the number of ticked tasks divided by the 30 tasks in the plan, shown as a percentage. A day's tab shows a green dot when all six of its tasks are ticked. Notes do not affect the percentage.
Can a design sprint be shorter than five days?
Yes. Many teams compress it to four days by combining mapping and sketching, and remote teams often spread it over two weeks. Keep the order (understand, sketch, decide, prototype, test) and keep the customer test; that is the part that makes it a sprint.
Is my design sprint checklist shared with my team?
No. Ticks and notes live in your browser's local storage under the key design-sprint and are not synced. Share the work by exporting the summary as Text, Image or PDF, or keep the checklist on the facilitator's screen during sessions.
Is there an in-depth guide to the Design Sprint Checklist?
Yes. “Design Sprint vs Foundation Sprint: How the Two Knapp Sprints Work” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.