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 | ![]() Knowledge Modeling Concept Mapping | ![]() 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 | 1-2 h | Mehrere Wochen | 1 Tag bis mehrere Wochen |
Participantsdifferent | 2-8 | 1-8 | 2-6 researchers plus sample | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Issue Map, Positions, Argument Notes | Concept Map, Relationship Labels, Knowledge Gaps | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | RationaleKnowledgeDecision | KnowledgeConceptsMappingSensemaking | OutcomesInnovationResearchQuantitative | InnovationPrototypeResearch |



