Design Sprint Facilitator: How to Facilitate a Sprint

How to facilitate a design sprint: the design sprint facilitator keeps time, captures discussion, protects energy and hands decisions to the Decider.

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

The design sprint facilitator runs the process so the rest of the team can concentrate on the work. The checklist from Jake Knapp and John Zeratsky defines the role in one line: the Facilitator "will manage time, conversations, and the overall sprint process," and should be "someone who's confident leading a meeting and synthesizing discussions on the fly" (Design Sprint guide). The same guide answers the question of experience directly: you can facilitate without it, using the book and the template.

Design sprint facilitation is distinct from deciding. The Facilitator does not choose the target or the winning sketch; that is the Decider's job. The Facilitator makes sure the Decider has what they need to decide, at the right moment, and that decisions are recorded and not reopened. It helps if the Facilitator stays out of sketching and voting, which keeps them neutral and frees them to watch the room.

Most of the work is small and continuous. It includes starting and stopping every timebox, writing the essence of every discussion on the whiteboard, noticing when energy drops, calling a break, and moving a debate to the Decider before it eats the afternoon. The checklist's Monday facilitator tips name the core habits: ask the group for permission to facilitate, "ABC: Always be capturing," ask obvious questions, take care of the humans, and "decide and move on" (Design Sprint guide).

For remote sprints, the role grows. The Remote Design Sprint Guide recommends a second facilitator who "should focus on the people, not the process" and reach out to anyone who is not participating (Remote Design Sprint Guide). That guide and the remote sprint skill cover the online techniques in detail. The Google Design Sprint method page explains what each day is for; this skill covers how the Facilitator runs it.

How It Works

The Facilitator works from the checklist. On Monday morning they write it on the whiteboard and check items off through the day, so the team always knows where it stands. They open with introductions, point out the Facilitator and the Decider, and explain the process (Design Sprint guide). Asking permission to facilitate, and explaining that they will keep things moving, gives them standing to interrupt later.

Capturing is the Facilitator's main tool. During expert interviews and discussions, they write short summaries on the whiteboard and keep asking "How should I capture that?" A captured point can be pointed at, voted on and revisited. An uncaptured one gets repeated. Asking obvious questions, including "why?", brings out assumptions that insiders have stopped noticing.

Timeboxes carry the schedule. Every activity has a length, from three minutes per Lightning Demo to eight minutes for Crazy 8s, and the checklist recommends a Time Timer so the remaining time is visible. The checklist also suggests two timers: one for the current activity and one to remind the Facilitator when to take a break. Breaks come every sixty to ninety minutes, with a snack break mid-morning and a late lunch.

Decisions go to the Decider. When a debate stalls, the Facilitator asks the Decider to make a call, following the checklist's "Decide and move on." On Wednesday the tip is "Don't drain the battery": tough decisions go to the Decider, small ones wait until the next day, and new abstract ideas are kept out of the storyboard. The Facilitator also protects the silent, individual exercises on Tuesday and Wednesday from turning into group discussion.

The Facilitator's role shifts across the week. On Monday they lead from the whiteboard. On Tuesday and Wednesday they run exercises and keep time. On Thursday they help coordinate the build, sometimes acting as the Stitcher in a small team, and make sure the trial run happens. On Friday they set up the observation room and scorecard and keep the team focused on the sprint questions.

Step-by-Step Guide

Step 1: Prepare the run of show

Before the sprint, turn the agenda into a Facilitator's script: each activity, its length, what you will say to introduce it and what artifact it should produce. Check that the Decider knows which moments need them. Prepare the room or online board with the goal, questions and map areas laid out. Have timers, dots, pens and paper ready so no exercise waits for supplies.

Step 2: Open the sprint and set the norms

Write the checklist on the whiteboard, run introductions and point out who is the Facilitator and who is the Decider (Design Sprint guide). Explain the process in a few minutes. Ask the group for permission to facilitate and to keep things moving. Agree the ground rules, such as shutting down messaging and stepping out for calls.

Step 3: Run Monday from the whiteboard

Lead the long-term goal and sprint questions, drawing out both optimism and pessimism. Draw the map while the team directs. During expert interviews, capture the key points on the whiteboard and update the goal, questions and map as you go. Keep How Might We notes flowing, time the organizing step, and hand the target choice to the Decider at the end of the day.

Step 4: Protect the silent work on Tuesday

Time each Lightning Demo and capture ideas as quick sketches. Explain each step of the four-step sketch briefly, then keep the room quiet and the timer visible. Reassure people who say they cannot draw that sketches only need to communicate. Collect the finished solution sketches without letting anyone present them.

Step 5: Run the decision on Wednesday

Set up the art museum and give clear instructions for each step of the sticky decision: heat map, speed critique, straw poll and supervote (Design Sprint guide). During the speed critique, keep to three minutes per sketch and capture the standout ideas and objections. After the supervote, lead the storyboard, taking a break first and sending tough calls to the Decider so the team's energy lasts.

Step 6: Keep Thursday on track

Help the team pick fast tools and assign roles, then check progress before lunch and early in the afternoon. If the team is small, act as the Stitcher. Make sure the trial run happens with enough time left to fix problems, and that the Interviewer has written the script. Confirm Friday's customers are reminded.

Step 7: Run Friday's observation and verdict

Set up the scorecard grid and the video feed before the first interview. Keep observers taking notes and voting after each session, and give the Decider the final call on each cell (Design Sprint guide). At the end of the day, lead the review of the scorecard, collect hot takes and next steps, and ask the Decider to decide. Record the outcome and thank the team.

Best Practices

• Always be capturing. Writing the essence of every discussion on the whiteboard, as the Design Sprint guide recommends, turns talk into material the team can use later in the week.
• Stay neutral. A Facilitator who pushes their own ideas loses the room's trust; if you have a strong view, share it as an expert interview on Monday and then step back.
• Watch energy as closely as time. Break every sixty to ninety minutes and before hard exercises such as the storyboard.
• Hand debates to the Decider quickly. A short debate that ends in a decision costs less energy than a long one that ends in compromise.
• Use a co-facilitator for remote sprints. The Remote Design Sprint Guide recommends a second person focused on the people while the first runs the process.
• Keep the checklist visible. Checking items off in front of the team makes progress concrete and makes it obvious when an activity is overrunning.

Common Mistakes

• Facilitating and deciding at the same time: A Facilitator who picks winners takes the Decider's role and loses neutrality. Put every final call to the Decider.
• Letting silent exercises turn into discussion: Talking during sketching or the heat map anchors the room on the loudest idea. Keep those steps quiet and hold discussion for the critique.
• Skipping breaks when behind schedule: Tired teams make slower, worse decisions. Take the break and shorten the next activity instead.
• Failing to capture: Points that are only spoken get lost or repeated. Write them on the whiteboard as they come up.
• Reopening decisions: Revisiting Monday's target on Wednesday burns time and energy. Note new concerns for later and keep to the decisions already made.

References

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

Related Skills

• Planning a Design Sprint Agenda and Schedule
• Running a Remote Design Sprint with Distributed Teams
• Design Sprint Exercises: Sketching and Voting
• Design Sprint Day 1: Map the Problem and Pick a Target

Sources

• Jake Knapp and John Zeratsky: Design Sprint guide
• 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.