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 Kanban |  Product Strategy Impact Mapping |  Business Strategy PESTLE 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 work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | Ongoing | 45-90 min | 1-3 h |
Participantsdifferent | 2-8 | 2-12 | 3-8 | 2-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Kanban board, WIP policies, Flow metrics | Impact Map, Outcome Hypotheses, Delivery Options | PESTLE Map, External Risks, Strategic Questions |
Tagsno overlap | StrategyAnalysisPlanning | FlowVisual managementDelivery | OutcomesStrategyBehaviorPlanning | StrategyMarketAnalysis |