Design Sprints assist teams in testing innovative ideas within a short timeframe. By combining design thinking and agile methods, the process is structured and purpose-driven.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
A Design Sprint is a five-day, tightly timeboxed process that helps teams quickly validate an important question through ideas, prototypes, and user tests.
The Design Sprint emerged at GV from the work of Jake Knapp. He introduced sprint formats at Google in 2010 and brought them to GV in 2012, where the team distilled the approach into a fixed five-day method. The goal was to avoid endless debate and costly upfront implementation by answering critical product questions in one week with a realistic prototype and customer tests.
The sprint works like a tightly guided decision path. Monday narrows the problem to a goal and focus, Tuesday generates competing solution ideas, Wednesday selects one direction, Thursday turns it into a realistic prototype, and Friday tests it with real users. Each phase shrinks the search space and moves risk forward.
Each step has a fixed time limit so the team can move quickly and avoid endless discussion.
At the start, the team selects one concrete, important question to concentrate its effort on.
The team first creates multiple options and then narrows them to one viable direction.
What gets built is a credible but intentionally incomplete surface that makes an idea testable.
Real reactions to the prototype reveal whether the solution deserves further investment.
A Design Sprint is useful when a team needs fast learning before a larger investment, such as for new product ideas, features, market opportunities, or messaging. It works best for well-defined questions with reachable users and decision-makers in the room. It does not replace long-term product development or launch work; its value depends on a sharp focus, the right participants, and disciplined use of the time window.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.