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 |  Engineering Failure Scenario Analysis |  Growth A/B Testing |
|---|---|---|---|
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. | 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. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 30–45 min | 1-3 h | 1-4 Wochen |
Participantsdifferent | 1-10 | 3-8 | 1-6 |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Experiment results, Decision log, Learning summary |
Tagsno overlap | FramingOpportunityIdeationQuestions | FailureResilienceRisk | ExperimentsGrowthAnalyticsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
