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 |  Business Strategy Value Chain Analysis |  Product Strategy Impact Mapping |  Business Strategy GAP Analysis |
|---|---|---|---|---|
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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 30-240 min | Half day | 45-90 min | 1-3 h |
Participantsdifferent | 1-6 | 3-8 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Value Chain Map, Lever List | Impact Map, Outcome Hypotheses, Delivery Options | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | StrategyBusiness modelDiagnosisAnalysis | OutcomesStrategyBehaviorPlanning | StrategyAnalysisPlanning |