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 GAP Analysis |  Operations A3 Problem Solving |  Business Strategy Value Chain 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. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 30-240 min | 1-3 h | 45-90 min | Half day |
Participantsdifferent | 1-6 | 2-8 | 2-5 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Gap Matrix, Action Plan, Risk Notes | A3 Report, Action Plan, Root Cause Analysis | Value Chain Map, Lever List |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | StrategyAnalysisPlanning | LeanProblem solvingCoachingOperations | StrategyBusiness modelDiagnosisAnalysis |