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 Knowledge Mapping |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Decision Jam |  Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 h | 30-240 min | 60-90 min | Half day |
Participantsdifferent | 3-12 | 1-6 | 4-10 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Problem Cluster, Prioritized Challenge, Experiment | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | KnowledgeMappingRisk | TroubleshootingProblem solvingDiagnosis | FacilitationDecisionProblem solvingWorkshop | StrategyBusiness modelRiskDiagnosis |