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 |  Operations Getting Things Done |  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. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | 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 | 1-2 h Setup, laufend | 1-3 h |
Participantsdifferent | 1-6 | 3-8 | 1 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Value Chain Map, Lever List | Action Lists, Project List, Review Routine | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | StrategyBusiness modelDiagnosisAnalysis | ProductivityPlanningTasksExecution | StrategyAnalysisPlanning |