Design Sprint
A time-boxed process, classically five days, that takes a team from a hard product question to a tested prototype without building anything.
Process & MethodsThe sprint compresses the usual cycle: understand the problem, sketch options, decide on one, build a realistic prototype, and test it with real users at the end of the week. Its real function is forcing a decision. A question that has circled leadership for two months gets settled on Wednesday because the schedule leaves no room to defer it.
Sprints are the wrong tool for incremental work. They are expensive — five people for five days — and they answer one big question, so running one to decide button placement wastes the format. They fit best before a commitment: a new product line, a pricing change, a platform bet where being wrong costs a quarter.
In practice
A DeFi team could not agree whether to hide or expose gas mechanics. A sprint produced two prototypes tested with eight traders on Friday. Before: three months of internal debate. After: exposed gas with a plain-language default won clearly, and the decision held. The catch — the winning prototype needed engineering work the sprint had not estimated.
Learn more
You may ask
Frequently Asked Questions
Does a design sprint have to be five days?
No, and most are not. Four-day and even two-day variants work if the problem is narrower and the team is small. What cannot be cut is the user test at the end — without it the sprint produces a confident guess.
Who needs to be in the room?
Someone who can decide, someone who knows the customers, someone who knows what is technically feasible, and a designer. Missing the decider is the most common reason a sprint ends without a decision.
Related terms
All terms- PrototypingBuilding a simulated version of a product or flow — from paper to clickable to coded — in order to test an idea before committing to it.
- Usability TestingWatching real users attempt real tasks in a product or prototype to find where they struggle, without steering them.
- Design ThinkingA problem-solving approach that starts from user needs and moves through framing, ideation, prototyping and testing before committing to a solution.
- MVP (Minimum Viable Product)The smallest version of a product that delivers real value to real users and produces evidence about whether the idea works.
Let's talk about your product.
Happy to look at what you're building and say where design would move the needle.
Contact Us