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 Strategy Map |  Operations A3 Problem Solving |  Operations After-Action Review |  Operations Kepner-Tregoe |
|---|---|---|---|---|
Purposedifferent | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 2-4 h workshop plus review | 45-90 min | 20-45 min | 2-8 h |
Participantsdifferent | 4-10 | 2-5 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Strategy Map, Objective Set, Cause-Effect Hypotheses | A3 Report, Action Plan, Root Cause Analysis | Lessons learned, Action items, Event summary | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | AlignmentExecutionGoalsCausality | LeanProblem solvingCoachingOperations | LearningOperationsImprovement | Problem solvingRoot causeDecisionOperations |