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 |  Operations Weekly Review |  Business Strategy GAP Analysis |  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. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. | 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. | 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 | Low | Medium | High |
Timedifferent | 30-240 min | 30-60 min | 1-3 h | Half day |
Participantsdifferent | 1-6 | 1 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Updated Task System, Weekly Focus, Next Actions | Gap Matrix, Action Plan, Risk Notes | Value Chain Map, Lever List |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ProductivityExecutionPlanning | StrategyAnalysisPlanning | StrategyBusiness modelDiagnosisAnalysis |