View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Knowledge Modeling Concept Mapping |  Product Discovery Smoke Test |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-2 h | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 3-8 | 1-8 | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop | Workshop + async | Async | Async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Concept Map, Relationship Labels, Knowledge Gaps | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | FailureResilienceRisk | KnowledgeConceptsMappingSensemaking | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |