Design sprint

What it means

A design sprint is a structured five-day process in which a team understands a problem, sketches solutions, picks one, builds a prototype and tests it with real users. Google Ventures popularised it as a way to validate an idea in a week rather than months of development.

It draws on design thinking but is strictly time-boxed. Each day has a clear job: Monday maps the problem, Tuesday sketches, Wednesday decides, Thursday builds the prototype and Friday runs interviews with five users.

The result is not a finished product but tested knowledge of whether the solution makes sense. A sprint precedes building an MVP or a large investment and reduces the risk of building something customers do not want.

How it works in practice

A sprint involves a small team of up to seven people, including a decider with authority to choose the direction. At the start the team clarifies the goal, the key questions and the target user, for example based on a prepared buyer persona.

The prototype should look real but need not work: clickable screen mock-ups, a draft flyer or a simulated service are enough. Friday's tests run as usability testing, with the team watching where people get stuck and what they do not understand.

After the sprint comes a decision: continue, adjust and test again, or drop the idea. Findings feed into the product roadmap and backlog so that the insights do not stay on sticky notes in the meeting room.

What to watch out for

A sprint needs the team's full attention all week. If people deal with routine work alongside it, the result tends to be weak. It should therefore be planned ahead and protected from meetings and e-mail.

Five interviews reveal the main usability problems but do not prove market demand. A positive reaction from testers does not mean customers will pay, so after the sprint the business model and willingness to pay should be validated too.