View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling IBIS | ![]() Decision Making Cynefin Workshop | ![]() Product Discovery Outcome-Driven Innovation | ![]() Innovation Design Thinking |
|---|---|---|---|---|
Purposedifferent | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | 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. | 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. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 1-3 h | 60-180 min | Mehrere Wochen | 1 Tag bis mehrere Wochen |
Participantsdifferent | 2-8 | 4-20 | 2-6 researchers plus sample | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Issue Map, Positions, Argument Notes | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | RationaleKnowledgeDecision | ComplexitySensemakingDecision | OutcomesInnovationResearchQuantitative | InnovationPrototypeResearch |



