Planning a Design Sprint Agenda and Schedule

Design sprint planning: choose four or five days, book the Decider and team, recruit customers and write a day-by-day design sprint schedule.

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

Design sprint planning is the work that happens before Monday: choosing the challenge and format, securing the people, booking time and space, recruiting test customers and writing the agenda. Many problems that surface mid-week, such as an absent Decider, a missing expert or no customers on Friday, trace back to planning. Google's Design Sprint Kit puts it plainly: "Preparing for your Design Sprint is as important as the running of the Sprint itself," and it advises "at least one full day planning for each day that you are Sprinting" (Design Sprint Kit: Planning).

The published five-day sprint gives a ready-made agenda. The checklist from Jake Knapp and John Zeratsky starts with a "Set the Stage" list: choose a big challenge, get a Decider (or two), recruit a team of seven people or fewer, schedule extra experts, pick a Facilitator, block five full days and book a room with two whiteboards or set up online tools (Design Sprint guide). The day-by-day design sprint agenda that follows has approximate times for every activity from Monday's goal to Friday's last interview.

Many teams consider a shorter format, and this skill includes how to choose. AJ&Smart's Design Sprint 2.0 is a 4 day design sprint that fits the same core exercises into four days and needs experts for only the first two (AJ&Smart). Google's kit treats length as flexible and describes sprints that "can range from 1 to 5 days." Knapp and Zeratsky's current guide takes the opposite view for first-timers: asked whether teams really need five days, it answers yes, especially the first time. The Google Design Sprint method page compares these versions in more detail.

The output of planning is a short set of artifacts: a one-page sprint brief with the challenge and the Decider, a schedule with times, a list of people and when they are needed, a supplies or tools list, and a recruiting plan for Friday. The planner is usually the Facilitator. This skill is about assembling those artifacts in the right order, so nothing that takes lead time is left until the sprint week.

How It Works

Planning moves from decisions to logistics. The first decisions are whether the challenge deserves a sprint and who the Decider is. Google's kit says a sprint suits a set of conjectures or questions a team needs to explore, and that with a clear direction and agreed feature set "you probably don't need a Sprint" (Design Sprint Kit FAQ). If no one with real authority will join, or appoint a delegate who can, the checklist warns that decisions "won't stick."

Next comes the format. The published schedule runs from 10am to 5pm Monday to Thursday and from 9am to 5pm on Friday, with a snack break around 11:30am and lunch around 1pm, per the Design Sprint guide. The four-day version puts expert interviews, the map, Lightning Demos and sketching on day one, the decision and storyboard on day two, the prototype on day three and testing on day four (AJ&Smart). Choose by team experience, calendar realities and how much is unknown about the problem.

People come next. The core team stays all week. Google's kit suggests roles such as a UX designer, a user researcher, a product manager, an engineer, marketing and content strategy, and says to include the people who will carry the work forward after the sprint (Design Sprint Kit FAQ). Experts need short, fixed slots; the checklist plans for two to three hours of interviews in total on Monday afternoon.

Recruiting has the longest lead time. Someone needs to own it, with a screener survey and follow-ups, and it takes one or two extra hours a day during the sprint. Book five customers plus a backup for the last day, and plan thank-you incentives.

The last layer is the room and supplies. The checklist lists whiteboards, sticky notes, felt-tip pens, printer paper, small and large dot stickers in different colors, and two Time Timers. For a remote sprint, the equivalents are an online whiteboard template, a video tool, and a short tool check with the team the week before (Remote Design Sprint Guide).

Step-by-Step Guide

Step 1: Confirm the challenge and the Decider

Write the challenge in a sentence and check that it is important, uncertain and testable with a prototype. Identify the Decider and ask for their commitment to attend, or to appoint a delegate who can decide on their behalf (Design Sprint guide). If the challenge is already solved or no one can decide, postpone the sprint. Record both in a one-page sprint brief.

Step 2: Choose the format and length

Decide between the five-day schedule, a four-day variant or a shorter workshop. For a first sprint, or a problem the team knows little about, choose five days, as Knapp and Zeratsky recommend for first-timers. Consider four days when the team has sprint experience and senior people cannot give a full week. Whatever you pick, keep every phase: mapping, sketching, deciding, prototyping and testing.

Step 3: Recruit the team and book the experts

Invite up to seven core participants with different skills, including the people who work on the project day to day, and name the Facilitator. Ask each person to clear their calendar for the whole sprint. List the experts the team needs to hear from and book them into short slots on the first afternoon. Send everyone the brief so they arrive knowing the challenge.

Step 4: Start recruiting customers

Put one person in charge of recruiting as soon as the target customer is roughly known. Write a screener survey that finds the right people without revealing who you are looking for, find candidates where they spend time or use a recruiting service, and follow up by email and phone (Design Sprint guide). Aim for five confirmed customers plus at least one backup. Book a second room or a video link for the interviews.

Step 5: Write the design sprint schedule

Lay out each day hour by hour, starting from the published checklist or the four-day agenda. Include breaks every sixty to ninety minutes and a late lunch, which the checklist says maintains energy. Mark where the Decider must be present and where experts join. Put the schedule on a whiteboard or a shared document everyone can see.

Step 6: Prepare the space, supplies and tools

Book one room for the whole sprint and a second for testing day, or set up an online board and video tool. Buy the supplies on the checklist: whiteboards or equivalent surfaces, yellow sticky notes, black pens and markers, printer paper, dot stickers in two colors and timers. For a remote sprint, load the board template and run a short tool check with the team the week before (Remote Design Sprint Guide).

Step 7: Brief the team and plan the follow-up

A few days before the sprint, send the brief, the schedule and the ground rules, such as shutting down messaging and media during sessions, as the checklist asks. Meet the Decider to agree how decisions will be made. Plan what happens after Friday, including who will act on the result and when the team will review it. Google's kit recommends planning post-sprint steps before the sprint begins (Design Sprint Kit FAQ).

Best Practices

• Plan in proportion to the sprint. Google's kit advises at least a day of planning per sprint day (Design Sprint Kit: Planning), and most of that time goes to people and recruiting.
• Start recruiting first. Customers take longer to find and confirm than any other part of the sprint, and Friday fails without them.
• Keep every phase when you shorten. A shorter agenda can compress exercises, but dropping the test or the decision removes what makes it a sprint.
• Protect the Decider's time explicitly. Book the Decider for the moments the agenda needs them, and agree a delegate in advance in case they are called away.
• Write the agenda where everyone sees it. The checklist starts Monday by writing it on a whiteboard, which keeps the group aware of time.
• Buy supplies once and reuse them. A standing sprint kit of pens, notes, dots and timers makes later sprints faster to set up.

Common Mistakes

• Compressing the week by skipping the test: A sprint without Friday's interviews ends with opinions and no customer evidence. Keep the test, and shorten other activities if needed.
• Recruiting customers too late: Leaving recruiting until the middle of the week risks an empty Friday. Start as soon as the target customer is clear.
• Inviting too many people: A large group slows every exercise. Keep the core team to seven or fewer and bring others in as short expert interviews.
• An absent or part-time Decider with no delegate: Decisions get reopened after the sprint. Secure the Decider's commitment or a named delegate before booking anything else.
• No plan for after the sprint: Results that nobody owns fade quickly. Name who will act on the outcome before Monday.

References

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

Related Skills

• Design Sprint Facilitator: How to Facilitate a Sprint
• Running a Remote Design Sprint with Distributed Teams
• Design Sprint Day 1: Map the Problem and Pick a Target
• Sprint User Testing: Running Design Sprint Day 5

Sources

• Jake Knapp and John Zeratsky: Design Sprint guide
• Google Design Sprint Kit: Planning
• Google Design Sprint Kit: FAQ
• AJ&Smart: What is a Design Sprint
• AJ&Smart: Step-by-step guide for Design Sprint beginners
• 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.