View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Innovation Design Thinking |  Product Discovery Outcome-Driven Innovation |
|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. |
Complexitydifferent | Low | High | High |
Timedifferent | 30 min Setup, dann laufend | 1 Tag bis mehrere Wochen | Mehrere Wochen |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 4-10 | 2-6 researchers plus sample |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Problem Statement, Prototype, Test Learnings | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses |
Tagsno overlap | RiskTrackingStakeholdersGovernance | InnovationPrototypeResearch | OutcomesInnovationResearchQuantitative |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
