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 |  Product Strategy Impact Mapping |  Product Strategy GIST Planning |
|---|---|---|---|---|
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. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | GIST Planning helps clarify target groups, value, goals, and priorities. It links customer value, product logic, and decision priorities, and captures the result as goals, an idea bank, and a step-project list. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 30-240 min | 45-90 min | Wochen bis Monate je Goal |
Participantsdifferent | 2-8 | 1-6 | 3-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Impact Map, Outcome Hypotheses, Delivery Options | Goals, Idea bank, Step-project list, Tasks, Learning reports |
Tagsno overlap | StrategyAnalysisPlanning | TroubleshootingProblem solvingDiagnosis | OutcomesStrategyBehaviorPlanning | RoadmapOutcomesPlanningExperiments |