Complete firstClear scope
Agree the subject, boundary and decision before filling the model.
A broad or mixed scope produces a misleading model.
Method guideInnovation
Design Sprint
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityHigh
Time4-5 Tage
Participants5-8
FormatWorkshop
MaturityCanonical
01
Prerequisite
What needs to be finished first
Complete firstAccess to relevant evidence
Bring source material and people who know the work; distinguish facts from assumptions.
Unverified interpretations become false certainty.
02
Preparation
What needs to be ready before start
Materials
Shared visual workspace, source evidence, and an agreed decision question.
People / roles
Decider, facilitator, cross-functional sprint team, target users for testing.
Pre-read
Collect existing data, examples, constraints and relevant stakeholder perspectives.
Time needed
Five consecutive days with a dedicated team; recruit and prepare beforehand.
Setup
Choose a consequential question, long-term goal, target users and sprint team. Generate solution sketches individually after shared understanding; do not converge too soon. Critique sketches, select one direction and storyboard a testable experience. Build only enough fidelity to make the critical interaction credible to participants. Observe target customers completing tasks; record evidence and decide what to learn or test next.
03
Core question
The one question this method answers
Can a prototype test the riskiest assumption with target users?
04
Flow
Phases with goal, actions, output and pitfall
Moves a team from a consequential question to a testable prototype and customer evidence in a structured sprint.
Design Sprint record
Fictional worked example
Fictional sprint question: “How might a patient find a suitable follow-up without calling the practice?” Monday: map the journey and choose a target, interview experts. Tuesday: sketch independently. Wednesday: decide and storyboard the test. Thursday: build a clickable booking prototype. Friday: test with five recruited relevant patients; findings are qualitative, not market validation.
Understand and map
Bound the long-term goal, user and challenge.
Fictional: find a follow-up without calling.
Sketch
Sketch solution approaches independently.
Several booking entry points sketched.
Decide
Choose a direction and test story transparently.
SMS link leads to slot selection.
Prototype
Build a credible test prototype, not a production solution.
Clickable booking flow.
Test
Observe target users and separate findings from interpretation.
Sign-in barrier observed; qualitative finding.
The example text is fictional; replace it with sourced project information.
- 1
Challenge
Choose challenge and goal
Goal
Sprint brief
Inputs for this step
- Decision question, user access and decider
Actions
- State a consequential, bounded question, long-term goal and test focus; secure access to target participants.
Output
Sprint brief
Sprint brief
Quality check
Can a prototype test this question in the chosen sprint?
Pitfall
The team tackles an organization-wide strategy issue. Narrow to one critical moment and user need.
Timing: Allow time according to scope and evidence; no universal duration.
- 2
Sketch
Sketch solutions independently
Goal
Independent solution sketches
Inputs for this step
- Expert knowledge, journey and problem evidence
Actions
- Create individual notes and then silent solution sketches; ask each person to explain their concept.
Output
Independent solution sketches
Independent solution sketches
Quality check
Are alternatives visible before selection?
Pitfall
The loudest person anchors the solution early. Work silently first, then share ideas comparably.
Timing: Allow time according to scope and evidence; no universal duration.
- 3
Decide
Decide and storyboard
Goal
Decision rationale and storyboard
Inputs for this step
- Sketches, agreed criteria and decider
Actions
- Critique against the question, choose one direction transparently and storyboard a complete testable experience.
Output
Decision rationale and storyboard
Decision rationale and storyboard
Quality check
Does every scene lead to an observable test moment?
Pitfall
A compromise combines incompatible ideas. Choose a coherent approach and record alternatives.
Timing: Allow time according to scope and evidence; no universal duration.
- 4
Test
Prototype and learn
Goal
Observation notes and next decision
Inputs for this step
- Storyboard, suitable prototype and invited users
Actions
- Build only credible fidelity; observe tasks without leading and separate behaviour, quotes and interpretation.
Output
Observation notes and next decision
Observation notes and next decision
Quality check
Are observation and interpretation kept separate?
Pitfall
Positive reactions are treated as usability or market proof. Probe behaviour and limits; plan stronger evidence next.
Timing: Allow time according to scope and evidence; no universal duration.
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Moves a team from a consequential question to a testable prototype and customer evidence in a structured sprint. Record scope, evidence, assumptions, owner and next review in the versioned artifact.
Versioning / ownership
Record scope, date, participants, source version and owner. Note changed assumptions and the reason for each revision.
Tool alternatives
- Shared whiteboard or paper template
- Source links, records or measurement data
design-sprint-working-template.md
Prepare the decision, source evidence and next review.
Design Sprint: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Run the method Time: See catalog planning range; no universal duration.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Shared visual workspace, source evidence, and an agreed decision question.
- Roles: Decider, facilitator, cross-functional sprint team, target users for testing.
- Advance information: Collect existing data, examples, constraints and relevant stakeholder perspectives.
- Overall time needed: Five consecutive days with a dedicated team; recruit and prepare beforehand.
- Setup: Choose a consequential question, long-term goal, target users and sprint team. Generate solution sketches individually after shared understanding; do not converge too soon. Critique sketches, select one direction and storyboard a testable experience. Build only enough fidelity to make the critical interaction credible to participants. Observe target customers completing tasks; record evidence and decide what to learn or test next.
Prepare for the work steps
Challenge: Choose challenge and goal
- Decision question, user access and decider
Sketch: Sketch solutions independently
- Expert knowledge, journey and problem evidence
Decide: Decide and storyboard
- Sketches, agreed criteria and decider
Test: Prototype and learn
- Storyboard, suitable prototype and invited users
Design Sprint record
Understand and map
Bound the long-term goal, user and challenge.
...
Sketch
Sketch solution approaches independently.
...
Decide
Choose a direction and test story transparently.
...
Prototype
Build a credible test prototype, not a production solution.
...
Test
Observe target users and separate findings from interpretation.
...
This blank document contains only section prompts.
5-Day UX Design Sprint · Google Design
Challenge: Choose challenge and goal
Expected artifact: Sprint brief
Sprint brief
Entry:
...
- Can a prototype test this question in the chosen sprint?
Sketch: Sketch solutions independently
Expected artifact: Independent solution sketches
Independent solution sketches
Entry:
...
- Are alternatives visible before selection?
Decide: Decide and storyboard
Expected artifact: Decision rationale and storyboard
Decision rationale and storyboard
Entry:
...
- Does every scene lead to an observable test moment?
Test: Prototype and learn
Expected artifact: Observation notes and next decision
Observation notes and next decision
Entry:
...
- Are observation and interpretation kept separate?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/design-sprint/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
design-sprint-beispiel.md
Concrete filled scenario, fictional example
Fictional sprint question: “How might a patient find a suitable follow-up without calling the practice?” Monday: map the journey and choose a target, interview experts. Tuesday: sketch independently. Wednesday: decide and storyboard the test. Thursday: build a clickable booking prototype. Friday: test with five recruited relevant patients; findings are qualitative, not market validation.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Choose challenge and goalThe team tackles an organization-wide strategy issue.View in phase
- Sketch solutions independentlyThe loudest person anchors the solution early.View in phase
- Decide and storyboardA compromise combines incompatible ideas.View in phase
- Prototype and learnPositive reactions are treated as usability or market proof.View in phase
Trap
Choose challenge and goal
Symptom
The team tackles an organization-wide strategy issue.
What to do
Narrow to one critical moment and user need.
Trap
Sketch solutions independently
Symptom
The loudest person anchors the solution early.
What to do
Work silently first, then share ideas comparably.
Trap
Decide and storyboard
Symptom
A compromise combines incompatible ideas.
What to do
Choose a coherent approach and record alternatives.
Trap
Prototype and learn
Symptom
Positive reactions are treated as usability or market proof.
What to do
Probe behaviour and limits; plan stronger evidence next.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Stop if the decision question or scope is disputed; align it first.
Stop if key inputs are unavailable; list what evidence is needed.
Stop if the group treats assumptions as observed facts.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.