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 Kanban |  Delivery Value Stream Mapping |  Business Strategy GAP Analysis |  Business Strategy PESTLE Analysis |
|---|---|---|---|---|
Purposedifferent | 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 delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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. | 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 | Ongoing | 1-3 h | 1-3 h | 1-3 h |
Participantsdifferent | 2-12 | 4-10 | 2-8 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | Gap Matrix, Action Plan, Risk Notes | PESTLE Map, External Risks, Strategic Questions |
Tagsno overlap | FlowVisual managementDelivery | LeanFlowWasteDelivery | StrategyAnalysisPlanning | StrategyMarketAnalysis |