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 |  Operations Weekly Review |  Business Strategy Balanced Scorecard |
|---|---|---|---|---|
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. | 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. | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 h | 30-240 min | 30-60 min | Halber Tag bis mehrere Wochen |
Participantsdifferent | 2-8 | 1-6 | 1 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Updated Task System, Weekly Focus, Next Actions | Balanced Scorecard, Strategic Measures, Initiative Map |
Tagsno overlap | StrategyAnalysisPlanning | TroubleshootingProblem solvingDiagnosis | ProductivityExecutionPlanning | StrategyMetricsExecution |