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 |
|---|---|---|---|
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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-240 min | 30-60 min | 1-3 h |
Participantsdifferent | 1-6 | 1 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Updated Task System, Weekly Focus, Next Actions | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ProductivityExecutionPlanning | StrategyAnalysisPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
