Turns ideas, open questions, and testable next steps into a tangible result by mapping the challenge, sketching solutions, and testing with users.
What solution sketch for the core sprint question yields a testable prototype in four days that can be tested with real users on Day 5?
The method helps clarify ideas, open questions, and testable next steps concretely. It opens up the thinking space, brings ideas together, and leads to testable options. The result is captured as a prototype, test findings, and decision rationale.
The team follows the steps: map the challenge, sketch solutions, decide, build the prototype, and test with users. Each step is captured visibly. At the end, a prototype, test findings, and decision rationale are available so decisions, tests, or actions can follow directly.
Method sketch for a quick mental model.
The runsheet guides execution with 5 phases, timeboxes, 6 pitfalls, and clear stop criteria.
Open runsheetDesign Sprint follows a clear working logic: mapping the challenge, sketching solutions, deciding, building a prototype, and testing with users. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, a prototype, test findings, and decision rationale support decisions, learning, or further planning.
Prepare a clear guiding question, the right information, and a visible workspace. Plan about 4-5 days with 5-8 people and use the format in a facilitated workshop. The facilitation is demanding and should be carefully prepared; short timeboxes, visible intermediate results, and a parking lot for open questions help.
Compact working template for Design Sprint with context, input, output artifacts, and next step.
A multi-day process to understand a problem, sketch solutions, prototype, and test.
When and for what do we use this method?
Which data, observations, decisions, or materials are available?
Short notes along the runsheet.
Owner, date, and success signal.
Short decision aid for existing alternatives.
Statt Design Sprint, wenn du mit Assumption Mapping Annahmen nach Unsicherheit und Risiko ordnen und dann gezielt testen willst.
Turns ideas, open questions, and testable next steps into a tangible result by performing empathy-based research, defining the problem, and testing and iterating with users.
Turns ideas, open questions, and testable next steps into a tangible result by setting a challenge, starting a timer, and voting or combining ideas.
Parallel design teams turn a shared challenge into comparable concepts, open questions, and a consolidated direction.
Alternating divergent and convergent phases keep problem framing and solution design visibly separated for product work.
Turns user actions, touchpoints, and design concepts into a tangible result by clarifying the problem and constraints, sketching individually, and iterating together.
Turns ideas, open questions, and testable next steps into a tangible result through defining a challenge, agreeing on rules, and clustering and selecting outcomes.