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 Hypothesis-Driven Troubleshooting |  Decision Making Red Teaming |  Knowledge Modeling Concept Mapping |  Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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. | 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 | High | Medium | High |
Timedifferent | 30-240 min | 1-4 h | 1-2 h | Half day |
Participantsdifferent | 1-6 | 3-8 | 1-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Challenge Findings, Risk Register, Mitigation Plan | Concept Map, Relationship Labels, Knowledge Gaps | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | RiskDecisionSensemaking | KnowledgeConceptsMappingSensemaking | StrategyBusiness modelRiskDiagnosis |