Innovation Process model
Moves a team from a consequential question to a testable prototype and customer evidence in a structured sprint.
Moves a team from a consequential question to a testable prototype and customer evidence in a structured sprint.
Can a prototype test the riskiest assumption with target users?
The steps are a practical sequence; adapt them to the method’s purpose and available evidence.
Challenge
State a consequential, bounded question, long-term goal and test focus; secure access to target participants.
Sketch
Create individual notes and then silent solution sketches; ask each person to explain their concept.
Decide
Critique against the question, choose one direction transparently and storyboard a complete testable experience.
Test
Build only credible fidelity; observe tasks without leading and separate behaviour, quotes and interpretation.
Revisit the model when evidence, context or outcomes change. Record what changed and why.
Use it when: High-risk Ideas, Product Concepts. The group can provide the evidence and authority the method requires.
Challenge, solution sketches, chosen story, prototype and qualitative test observations.
The artifact records scope, date, participants, source version, and owner, including changed assumptions and the reason for each revision.
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.
Bound the long-term goal, user and challenge.
Fictional: find a follow-up without calling.
Sketch solution approaches independently.
Several booking entry points sketched.
Choose a direction and test story transparently.
SMS link leads to slot selection.
Build a credible test prototype, not a production solution.
Clickable booking flow.
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.
State a consequential, bounded question, long-term goal and test focus; secure access to target participants.
When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.
The method compresses divergence and convergence into a fixed rhythm so insight, selection, and validation follow each other closely. Alternating between gathering, condensing, deciding, and testing quickly turns a broad search into a solid prototype path. The format also creates clarity about assumptions, uncertainties, and the next learning question.
A Design Sprint works because it brings problem understanding, selection, prototyping, and learning into a dense sequence, shortening long stretches of fuzziness. Its strength lies in not just generating variants but condensing them under decision pressure and translating them directly into testable hypotheses. A tightly scoped question, protected focus, and consistent grounding in user reactions remain essential so the sprint delivers real direction.
Prepare the decisive product question, existing evidence, and a small team with clear decision authority beforehand. Direction is often decided between idea generation and selection; the group needs the courage to narrow down there, or the sprint falls apart into interesting fragments. Close with a visible learning decision and a clear conclusion for the product or the next validation.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Your feedback helps shape the next improvements to methodatlas.
Prepare the decision, source evidence and next review.
To be confirmed
To be confirmed
Run the method Time: See catalog planning range; no universal duration.
Complete this worksheet on paper or in your own document during the work.
Bound the long-term goal, user and challenge.
...
Sketch solution approaches independently.
...
Choose a direction and test story transparently.
...
Build a credible test prototype, not a production solution.
...
Observe target users and separate findings from interpretation.
...
This blank document contains only section prompts.
5-Day UX Design Sprint · Google Design
Expected artifact: Sprint brief
Sprint brief
Entry:
...
Expected artifact: Independent solution sketches
Independent solution sketches
Entry:
...
Expected artifact: Decision rationale and storyboard
Decision rationale and storyboard
Entry:
...
Expected artifact: Observation notes and next decision
Observation notes and next decision
Entry:
...
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/design-sprint/run-sheet
Fitting alternatives with decision guidance, followed by other related methods.
Instead of Design Sprint, when you want to use Assumption Mapping to order assumptions by uncertainty and risk and then test them in a targeted way.
Brings research, problem statement, prototype, and test learnings into a continuous learning loop.
Forces eight sketches in a short time so direction options emerge and favorites become quickly comparable.
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.
Brings sketches, critique, and iteration together so solid design decisions grow out of early drafts.
