View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy GAP Analysis |  Engineering Hypothesis-Driven Troubleshooting |  Business Strategy PESTLE Analysis |  Business Strategy Value Chain Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends. | 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 | 1-3 h | 30-240 min | 1-3 h | Half day |
Participantsdifferent | 2-8 | 1-6 | 2-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | PESTLE Map, External Risks, Strategic Questions | Value Chain Map, Lever List |
Tagsno overlap | StrategyAnalysisPlanning | TroubleshootingProblem solvingDiagnosis | StrategyMarketAnalysis | StrategyBusiness modelDiagnosisAnalysis |