Design Sprint: How to Run One in 5 Weeks, From Prep to Roadmap
8 min read ยท 2026-10-11
A design sprint is a five-day process. A small team maps a problem, sketches solutions, picks one, builds a realistic prototype and tests it with real users. You leave with an answer to one big question before you spend months building the wrong thing.
Most guides only cover those five days. In practice, a sprint takes about five weeks. You need two weeks before it to pick the right challenge, book the team and recruit testers. You need two weeks after it to turn what you learned into roadmap decisions. The plan below covers all three parts.
The roadmap at a glance
Goal: Answer one critical product question with a tested prototype, then turn the result into clear roadmap decisions. Duration: 5 weeks (2 weeks of prep, 1 sprint week, 2 weeks of follow-up)
Frame the challenge (Week 1)
Agree on one challenge that is big enough to deserve a full week of work.
- Write the challenge as one question, for example "Will new users finish setup without help?"
- Name the Decider, the person who makes the final calls during the sprint.
- List what you already know: support tickets, analytics, past research, sales feedback.
- Write down the risk if you build without testing first.
Milestone: The Decider signs off on a one-sentence challenge.
Assemble the team and book users (Weeks 1 to 2)
Get the right people and the right testers on the calendar.
- Pick a team of seven people or fewer: Decider, facilitator, designer, engineer, and someone close to customers.
- Block all five days in every calendar, with no other meetings.
- Recruit five target users for Friday and send them a short screener.
- Book two or three experts for short interviews on Monday.
Milestone: Every team member has confirmed the full week, and five testers are booked.
Prepare the space and tools (Week 2)
Remove every practical blocker before Monday.
- Book one room, or set up a shared online whiteboard for a remote sprint.
- Gather supplies: sticky notes, markers, timers, dot stickers (small round stickers people use to vote), paper.
- Choose the prototype tool your designer already knows well.
- Write a daily agenda with time boxes for each exercise.
Milestone: The facilitator runs a 15-minute dry run of Monday with no missing tools.
Map and sketch (Sprint days 1 and 2)
Understand the problem, then come up with competing solutions.
- Monday: set a long-term goal, list sprint questions, draw a simple map of the user journey.
- Monday: interview experts and write "How might we" notes (short notes that turn a problem into a question), then pick one target moment on the map.
- Tuesday: review existing ideas from other products for inspiration.
- Tuesday: each person sketches alone. Start with notes and rough ideas, then do Crazy 8s (eight quick sketch variations in eight minutes), then draw a final three-panel solution sketch.
Milestone: A map with one target moment, and one finished solution sketch per person.
Decide and prototype (Sprint days 3 and 4)
Pick the strongest solution and make it look real.
- Wednesday: hang the sketches, vote silently with dot stickers (each person places small stickers on the ideas they like best), then let the Decider choose.
- Wednesday: draw a storyboard of 10 to 15 frames that shows the test from start to finish.
- Thursday: split prototype work into roles: makers, writer, asset collector, stitcher.
- Thursday: write the interview script and run one full rehearsal of the prototype.
Milestone: A clickable prototype that a stranger could use without explanation.
Test with users (Sprint day 5)
Watch real people use the prototype and spot patterns.
- Run five one-to-one interviews of about one hour each.
- One person interviews, and the rest of the team watches and takes notes.
- Mark each sprint question as positive, negative or neutral after every interview.
- End the day by listing patterns seen in three or more interviews.
Milestone: A written answer to each sprint question, backed by notes from five interviews.
Turn results into roadmap decisions (Weeks 4 to 5)
Make sure the sprint changes what the team builds next.
- Share a one-page summary: challenge, solution tested, patterns, decision.
- Choose one outcome: build, iterate and test again, or drop the idea.
- Break the winning concept into roadmap items with owners and target dates.
- Note open questions that need a follow-up test or more research.
Milestone: The roadmap is updated and the Decider has presented the decision to stakeholders.
What a design sprint is, and when to run one
A design sprint is a time-boxed method created at Google Ventures and described in the book "Sprint" by Jake Knapp. It packs months of debate into one week. The team does not ship code. It ships a prototype and real user reactions.
Skip it when the problem is small or the answer is already clear. A button color or a small bug fix does not need five people for five days. In those cases, use a quick test or simply ship and measure.
Run a sprint when the stakes are high and the answer is unclear. Good triggers:
- A new product or major feature that will take months to build.
- A key flow that users keep dropping out of, such as onboarding or checkout.
- A team stuck in debate, with no shared view of the right solution.
- A new market or customer type you have not served before.
The roles that make or break the week
A sprint fails most often because of people, not exercises. The Decider is the most important role. Without one in the room, Wednesday's decision drags on and the prototype ends up as a compromise that tests nothing.
If the Decider cannot attend all five days, ask them to join Monday morning and Wednesday. Then give the team written authority to decide the rest.
Keep the roles simple and agree on them in Week 1:
- Decider: makes the final call on the target, the solution and the next step.
- Facilitator: runs the clock, keeps the agenda and stays neutral on ideas.
- Designer: leads the prototype on Thursday.
- Engineer: checks what is technically realistic.
- Customer expert: someone from sales, support or research who hears from users every week.
How to run a remote design sprint
A remote sprint follows the same five days, with a few changes. Screen time is tiring, so many teams cut each day to about four or five focused hours. Some spread the sprint across more calendar days.
Sketching still works remotely. Ask people to draw on paper and upload a photo, or to sketch directly on the whiteboard. On Friday, run interviews on video. The team watches from a separate call so the tester only sees one person.
Set up these basics before Monday:
- One shared online whiteboard with a frame for each day.
- A video call link that stays the same all week.
- A timer everyone can see.
- A private chat channel for quick questions during silent work.
How to read Friday's results
Friday gives you patterns, not proof. Five interviews are enough to see the big problems in a flow, but not to measure how many users will convert. Treat the results as a strong signal for direction.
Sort what you saw into three groups. Strong positives are things most testers understood and liked without help. Clear failures are moments where several testers got stuck or confused. Mixed signals are reactions that split the group. Clear failures are often the most useful result, because they save you from building something that does not work.
Then decide. If the core idea worked, move the concept onto the roadmap and plan the build. If parts failed, fix those parts and run a shorter follow-up test. If the whole idea failed, you have saved weeks of work, so record the lesson and drop it.
How to connect the sprint to your roadmap
The biggest waste is a great sprint that changes nothing. Teams go back to their normal work on Monday, and the prototype sits in a folder. Weeks 4 and 5 exist to stop this.
Share the updated roadmap with the people who could not join the sprint. Show the prototype, a short clip or quote from testers, and the decision. This keeps the support you need for the build.
Translate the result into roadmap items people can act on:
- One item per user problem you confirmed, not per screen you designed.
- A clear owner and a rough time frame for each item.
- A milestone for the first real release, such as a beta for a small group of users.
- A separate item for open questions that need another test.
Common mistakes to avoid
- Picking a vague challenge like "improve the product". Frame one specific question that a single prototype can answer.
- Running the sprint without the Decider. Make sure they attend the key moments or give written authority to someone in the room.
- Building a polished prototype that takes too long. It only needs to look real enough for users to react honestly.
- Testing with friends or colleagues. Recruit five people who match your real target users.
- Letting meetings interrupt the week. Block all five days in every calendar before you start.
- Ending on Friday with no follow-up. Schedule the results review and roadmap update before the sprint begins.
Frequently asked questions
How long does a design sprint take?
The sprint itself takes five days. With preparation and follow-up, plan for about five weeks in total. Prep covers the challenge, the team and the testers. Follow-up turns the results into roadmap decisions.
How many people should be in a design sprint?
Keep the team at seven people or fewer. A typical team includes a Decider, a facilitator, a designer, an engineer and someone who talks to customers often. A bigger group slows down every decision.
What is the difference between a design sprint and a Scrum sprint?
A design sprint answers one question with a prototype and user tests, before any real building starts. A Scrum sprint is a repeating work cycle where a team builds and ships working product. Many teams run a design sprint first, then feed its results into their Scrum backlog.
Can you run a design sprint in less than five days?
Yes. Some teams use a four-day version that combines some exercises. Shorter formats work best when the team already knows the method well and the challenge is narrow. For a first sprint, keep the full five days so nothing gets rushed.