Guide6 min readUpdated
What Is a Design Sprint and Do You Need One? A Plain Guide
What is a design sprint? A plain guide to the 5 day sprint, how a workshop differs from the normal design process, and whether your startup needs one.
By Tithi Mondal, UI/UX Designer
A founder in Pune has an idea for a booking app. Her team has argued for three weeks about what to build first. Everyone has an opinion. Nobody has shown the idea to a customer. Someone says, "Let us run a design sprint."
A design sprint is a short, focused workshop, commonly about 5 days, in which a small team goes from a problem to a tested prototype. A prototype is a clickable demo that looks like the product but has no real working code behind it. The goal is to learn quickly whether an idea works, before spending months building it.
What is a design sprint?
A design sprint is a structured week of work with one question to answer: should we build this idea, and in what form? The team sets aside their usual work. They sit together, decide on one problem, and test one solution with real people at the end.
The general idea has three features.
- A fixed, short time. The days are planned in advance. There is no open-ended discussion.
- A small group. Often 5 to 7 people, including someone who can decide, such as the founder.
- A real test at the end. The team shows the prototype to a few target users and watches what happens.
It is not a way to build the full product. It is a way to choose a direction and reduce risk.
What happens in a 5 day sprint?
A 5 day sprint usually moves from understanding the problem, to sketching ideas, to deciding, to building a prototype, to testing it. Each day has one job.
- Day 1: Understand and choose a target. The team shares what it knows about customers and the problem. It picks one narrow thing to solve, such as "first-time users cannot book a slot without calling".
- Day 2: Sketch. Each person sketches possible solutions alone, on paper. Alone is deliberate. It stops the loudest voice from winning.
- Day 3: Decide. The team reviews the sketches and chooses the strongest ideas. It then plans the exact steps of the prototype. This planning is much like a user flow, which I explain as a plan of the steps for one task.
- Day 4: Build the prototype. A designer turns the plan into a clickable prototype. It only needs to look real enough for a test. For the difference between kinds of drafts, see wireframe vs mockup vs prototype.
- Day 5: Test. Five or so target users try the prototype one by one while the team watches. The team then writes what it learned.
The team ends the week with evidence, not opinions. Some ideas fail the test, and that result saves money.
What is the difference between a design sprint and the normal design process?
A sprint answers a risky question fast with the whole team in a room, while the normal design process builds a complete, polished design step by step over weeks. A sprint is a decision tool. The normal process is a production tool.
| Point | Design sprint | Normal design process |
|---|---|---|
| Main goal | Decide whether and how to build | Design the full product |
| Duration | About 5 days | Often 2 to 4 weeks for an app or website |
| Who takes part | The founder and a small team, all week | Mainly the designer, with feedback from the owner |
| Output | A rough prototype and test findings | Finished screens, prototype and developer files |
| Best when | The idea is unproven | The direction is known |
The two can work together. A sprint can come first and the normal process can follow, using the best parts of what the sprint proved.
Do startups need a design sprint?
A startup needs a sprint only when the main risk is "should we build this" and the team cannot agree or has no evidence. If the direction is already clear, a sprint can be an expensive detour.
A sprint helps in these cases.
- You have several competing ideas and no way to choose.
- You need to show something to investors or partners soon. See prototype for investor demo.
- You are about to spend a large sum on development and want to reduce the risk first.
- The team is divided, and a structured process will settle the argument with evidence.
A sprint is a poor fit in these cases.
- You already know your users and your main flows.
- You are redesigning a working product with small fixes. A UX audit fits better.
- The key people cannot give a full week. A sprint without the decision-maker present wastes the week.
- You have no access to target users for the test on day 5.
What can you do instead of a full sprint?
You can run a lighter version: one or two days of focused work, a simple prototype and a small test. Many small businesses do not need the full week.
A lighter path looks like this.
- Talk to a few real users first. Even five short calls teach a lot. See user research for startups.
- Decide the first version. Choose the smallest set of features that proves the idea. See MVP design: what to build first.
- Draw the main flow and a short prototype. Make just the key path clickable.
- Test with a handful of people. A phone call and a shared screen are enough. See usability testing on a small budget.
My own process begins with understanding the business and mapping the flow, which covers much of the same ground as the early sprint days, at a smaller scale. A full sprint adds value mainly through the team being together and deciding fast.
What does a good sprint contain, and what goes wrong?
A good sprint has one clear question, the right people in the room, a realistic prototype and real users on the last day. Most failures come from missing one of these.
Prepare these before the week starts.
- One written question, such as "Will first-time customers book a slot without calling us?"
- A decision-maker who stays all week.
- A list of 5 or so target users who can join on day 5.
- Any existing data, complaints and customer calls to share on day 1.
Common mistakes:
- A question that is too big. "Redesign the whole company" cannot fit in a week.
- Treating the prototype as the final product. It is a test, not a launch.
- Testing with friends and family. They are kind, and kind answers do not help.
- Ignoring the findings. Some teams run the sprint and then build what they first imagined.
- Skipping what comes next. After the sprint, someone must turn the result into a full design and a build plan.
How do a sprint and the normal design process affect cost and timeline?
A sprint costs the time of several people for 5 days, so the real cost is mostly your team's time plus the designer's time. The result is a faster decision, which can prevent a costly wrong build.
Prices for sprints vary widely, depending on the facilitator, the team size and the prototype detail. I will not quote a market figure. Compare the sprint cost with the cost of building the wrong thing. For the normal path, my app or website design usually takes 2 to 4 weeks, with two to three revision rounds included, and payment is 50% to begin and 50% on completion. UI/UX for apps and websites is a custom quote based on screens and user roles. For more on timing, see how long does design take, and for costs, UI/UX design cost in India.
If you are unsure whether you need a sprint or the normal process, tell me about your idea through contact and I will say which fits.
Frequently asked questions
How long is a design sprint?
The common format is 5 days. Shorter versions of 2 to 3 days also exist for smaller questions.
Who should attend a design sprint?
A small group of about 5 to 7 people, including a decision-maker such as the founder, someone who knows customers, and a designer.
Is a design sprint the same as a hackathon?
No. A hackathon aims to build working software quickly. A design sprint aims to test an idea with a prototype before building anything.
Can I do a design sprint for a small business?
Yes, in a lighter form. One or two focused days, a simple prototype and a test with a few customers often give most of the benefit.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.