View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Design Thinking |  Product Discovery Outcome-Driven Innovation |  Delivery RAID Log |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. |
Complexitydifferent | High | High | Low | Low |
Timedifferent | 1 Tag bis mehrere Wochen | Mehrere Wochen | 30 min Setup, dann laufend | 20-40 min initial, dann laufend |
Participantsdifferent | 4-10 | 2-6 researchers plus sample | 1-3 maintaining, briefing for everyone | 3-15 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Problem Statement, Prototype, Test Learnings | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | RAID Log, Status Report Source | ROAM Board, Owner List |
Tagsno overlap | InnovationPrototypeResearch | OutcomesInnovationResearchQuantitative | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment |