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 PESTLE Analysis |  Engineering Kanban |  Product Strategy Impact Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | Ongoing | 45-90 min |
Participantsdifferent | 2-10 | 2-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | PESTLE Map, External Risks, Strategic Questions | Kanban board, WIP policies, Flow metrics | Impact Map, Outcome Hypotheses, Delivery Options |
Tagsno overlap | StrategyMarketAnalysis | FlowVisual managementDelivery | OutcomesStrategyBehaviorPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
