Guide
How to run a remote design sprint
A remote design sprint follows the same arc as the in-person method from the book Sprint: understand the problem, sketch solutions alone, decide, build a prototype and test it with users. Online, shorten the sessions, keep ideas and votes private until they are revealed, name a facilitator and a Decider, and book testers before you start. AppSprint runs this arc as one guided room with video, private votes and AI-built prototypes, in about a day.
Where the design sprint comes from
The design sprint was developed by Jake Knapp at Google Ventures and described in the 2016 book Sprint, written with John Zeratsky and Braden Kowitz. The classic version takes five days: map the problem, sketch solutions, decide, build a realistic prototype, and test it with five customers.
Two ideas carry the method. People produce ideas alone before anything is discussed, so the loudest voice does not set the direction. And one person, the Decider, makes the final call, so the team does not stall in debate.
Before you start
- Name a facilitator to run the process and a Decider with real authority. See sprint roles.
- Keep the team small. The book recommends seven people or fewer.
- Book testers before the sprint begins. Recruiting is the step most likely to slip.
Run it step by step
Map the problem (2 to 3 hours)
Agree a long-term goal and map how a customer reaches it. Interview people who know the problem while everyone writes "How might we" notes. The Decider picks one customer and one moment to focus on.
Collect examples (about 1 hour)
Each person shows a product or idea worth borrowing from, about three minutes each.
Sketch alone (about 90 minutes)
Follow the four-step sketch: notes, rough ideas, Crazy 8s, then one detailed solution sketch. Work in silence, on paper.
Decide (about 2 hours)
Post the sketches without names. Review them in silence, mark strong parts with dots, discuss each sketch briefly, then vote privately. The Decider makes the final choice.
Build the prototype (up to a day)
Build only the surface a tester will touch. It has to look real enough to get an honest reaction.
Test with about five people
Give each tester realistic tasks, watch what happens, and look for patterns. See how to test a prototype with users.
Common mistakes
- Running full eight-hour days on video. Split the work into shorter blocks with real breaks.
- A Decider who drops in and out. If they cannot attend, they should name a delegate who can decide.
- Skipping the test. Without user feedback you have run a workshop, not a sprint.
What changes when the team is remote
Anonymity matters more. On a shared board, names and cursors show whose idea is whose and who voted first. Hide authorship until ideas have been judged, and reveal votes all at once.
Tool switching costs more, so use as few tools as you can. If time zones are far apart, do the solo steps separately and meet to review and decide.
Doing this in AppSprint
The Full Product Sprint follows the same arc in 22 guided steps: about one day, plus time for testers to reply. The Focused Product Sprint leaves out the goal, "How might we" and journey map steps and takes about half a day. The Prototype step is 45 minutes, because each person describes what people should be able to try and the AI builder returns a working prototype.
Notes stay hidden until the host shows them, ballots are private until the reveal, and the team vote is advisory: the decision-maker confirms each choice. AppSprint says host for facilitator, decision-maker for Decider, and Eight Quick Ideas for Crazy 8s.
Testing is a feedback form that testers open without an account, not a live interview, and AppSprint does not recruit testers or send the invitations. The agenda is fixed by the template and calls work best with about four cameras on, so a free-form canvas or a large workshop needs a different tool.