View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Process Mapping |  Business Strategy PESTLE Analysis |  Business Strategy GAP Analysis |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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. | 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-3 h | 1-3 h | 20-45 min |
Participantsdifferent | 3-10 | 2-10 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | PESTLE Map, External Risks, Strategic Questions | Gap Matrix, Action Plan, Risk Notes | Lessons learned, Action items, Event summary |
Tagsno overlap | ProcessOperationsImprovement | StrategyMarketAnalysis | StrategyAnalysisPlanning | LearningOperationsImprovement |