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 How Might We |  Knowledge Modeling IBIS |  Engineering Failure Scenario Analysis |
|---|---|---|---|
Purposedifferent | With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction. | 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. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30–45 min | 1-3 h | 1-3 h |
Participantsdifferent | 1-10 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Issue Map, Positions, Argument Notes | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions |
Tagsno overlap | FramingOpportunityIdeationQuestions | RationaleKnowledgeDecision | FailureResilienceRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
