Running a Remote Design Sprint with Distributed Teams

Run a remote design sprint: set up an online board and video, plan around time zones, adapt sketching and voting, and test with customers online.

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

A remote design sprint runs the same five days, the same exercises and the same roles as an in-person sprint, with the room replaced by an online whiteboard and a video call. Jake Knapp and John Zeratsky now treat remote as normal: their guide says "We run most of our sprints remotely" and offers an official Miro template to use with Zoom (Design Sprint guide). Teams also call this a virtual design sprint or a distributed design sprint; the mechanics are the same.

The main reference is the Remote Design Sprint Guide, which Knapp and Zeratsky put together with facilitator Jackie Colburn. They write that they had only been in a few sprints over video themselves, so they gathered input from more than 100 people "who have collectively run thousands of remote Design Sprints," and describe the result as an opinionated "greatest hits" guide (Remote Design Sprint Guide). Its tool picks include Zoom for video and Miro for the whiteboard; the guide notes it first recommended Mural in 2020 and later switched.

The most important finding is about time. The guide says teams may be tempted to shorten the process remotely, "but the community is unanimous in saying that it actually takes longer to run a remote sprint." It recommends sticking close to the book's schedule, which already has a break every 90 minutes or so, and adding more breaks for screen fatigue (Remote Design Sprint Guide). Time zones add a second constraint that an in-person sprint never has.

This skill covers setting up the board and tools, scheduling across time zones, adapting each day's exercises, keeping a remote group engaged, and running customer interviews over video. It assumes you know the in-person sprint; the Google Design Sprint method page explains the week, and the facilitation skill covers the Facilitator's core habits.

How It Works

The setup replaces the room. Everyone works on one shared board laid out in the same areas as the physical walls: goal and questions, map, How Might We notes, demos, sketches, decisions and storyboard. The Remote Design Sprint Guide suggests participants use two screens where possible, one for video and one for the whiteboard, so they can see teammates and the board at the same time (Remote Design Sprint Guide). The week before the sprint, the Facilitator holds a 30-minute session to explain the sprint, show the tools and check that every person can use them.

Time zones decide the schedule. The guide's approach has three cases. If everyone is in the same zone, follow the schedule from the book. If people are in adjacent zones, fit the schedule into the daytime hours everyone shares. If the team is spread across opposite sides of the world, one idea is to split into two or three groups that run their own competing sprints on the same challenge and share progress two or three times during the week.

Most exercises translate directly, with small changes. Sketching still happens on paper: the guide suggests making sure everyone has a Sharpie and plain printer paper, folding paper into thirds if there are no sticky notes, and then having everyone photograph their sketch and email it to the Facilitator so the art museum is ready on Wednesday morning. For the heat map, it quotes one facilitator who recreates dot stickers with draggable circles on the board instead of the built-in voting tools. The supervote uses a few large dots for the Decider.

Discussion needs more structure online. The guide recommends a co-facilitator who focuses on people rather than process, and a "Pass the Mic" routine in which everyone is muted and the Facilitator takes one person at a time off mute in a fixed order. It also recommends calling on people by name and a simple way for people to say they are stepping away. On Thursday, roles work as in the book, with breakout rooms for each group of builders, followed by a trial run with the whole team.

Customer tests need very few changes. The guide says a majority of the customer tests Knapp and Zeratsky ran with Michael Margolis at GV were done online. They also found that tracking answers to key questions in a spreadsheet was faster than sticky notes for observers.

Step-by-Step Guide

Step 1: Map where everyone is and set the schedule

List each participant's time zone and working hours. If everyone shares a zone, follow the book's schedule; if zones are adjacent, fit the day into the shared hours; if the team spans opposite sides of the world, consider competing sub-team sprints with overlap calls (Remote Design Sprint Guide). Keep the full sprint length and add extra breaks. Send calendar invitations for every session.

Step 2: Set up the board and tools

Create one board with areas for each day's work, laid out in the order the team will use them, and prepare templates for the map, sketches and storyboard. Knapp and Zeratsky offer an official template for this (Design Sprint guide). Choose one video tool and one whiteboard tool, and make sure everyone has access. Ask participants to have paper, a thick pen and, if possible, a second screen.

Step 3: Run the tool check and kickoff

The week before, hold a short session to explain how the sprint works and to let everyone practice with the board: adding notes, moving items and placing dots. Check each person's access and audio. Introduce the Facilitator, co-facilitator and Decider, and agree norms such as cameras on and how to signal a short absence. Fix access problems before Monday.

Step 4: Run Monday and Tuesday online

Run the goal, questions and map on the board with the Facilitator capturing, and invite experts into short video slots. Use Pass the Mic for rounds of input so everyone speaks in turn. For Lightning Demos, have people prepare their examples in their own area of the board. For the four-step sketch, give clear instructions, keep cameras on for timed work, and ask everyone to photograph their solution sketch and send it to the Facilitator at the end of the day.

Step 5: Run the decision and storyboard on Wednesday

Place the sketch photos in a row on the board for the art museum. Give each person draggable dots for the heat map and review in silence. Run the speed critique with strict timing, then the straw poll and the Decider's supervote with large dots (Remote Design Sprint Guide). Take a break before building the storyboard on a grid in the board.

Step 6: Build the prototype in breakout rooms

Assign the roles from the book (Makers, Stitcher, Writer, Asset Collector, Interviewer) and give each group of builders its own breakout room. Check in with the whole team at set times. Have the Stitcher combine the pieces in the afternoon and run a trial with everyone watching. Confirm each customer's appointment and send them the instructions for joining the call.

Step 7: Test online and close the sprint

Run the interviews on a video call with the observers hidden from the customer's view, and record the sessions with permission. Observers track the answers to each sprint question in a shared scorecard or spreadsheet. After each interview, vote and let the Decider record the answer. At the end of the day, review the scorecard together, collect next steps and share the board with anyone who needs the record.

Best Practices

• Budget extra time. The Remote Design Sprint Guide reports that remote sprints take longer, so keep the full schedule and add breaks.
• Test the tools with the team before the sprint. A short practice session prevents access and sign-in problems from eating Monday morning.
• Use a co-facilitator. One person runs the process while the other watches engagement and follows up with anyone who drifts.
• Keep sketching on paper. Pen and paper make sketches quick and equal, and a photo is enough to put them on the board.
• Structure turn-taking. Routines such as Pass the Mic prevent people talking over each other and give quieter participants a turn.
• Keep the board as the single record. Everything the team decides should be visible on the board, which also gives the team a lasting record of the sprint.

Common Mistakes

• Shortening the sprint because it is online: Cutting days to save video time leaves exercises rushed. The guide's community advice runs the other way: remote sprints need more time.
• Letting cameras go off during work: Without video, the Facilitator cannot see who is stuck or disengaged. Agree cameras-on as a norm at the kickoff.
• Replacing silent sketching with typed notes: Typing ideas into shared notes invites people to read and copy each other. Keep individual sketching on paper and share only the finished sketches.
• Ignoring time zones until the week starts: A schedule that works for one location can exhaust another. Plan the schedule around shared hours from the start.
• Unprepared customer calls: Customers who cannot join or share a screen cost a session. Send joining instructions in advance and check their setup.

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
• Planning a Design Sprint Agenda and Schedule
• Design Sprint Exercises: Sketching and Voting
• Sprint User Testing: Running Design Sprint Day 5

Sources

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