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 After-Action Review | ![]() Systems Thinking Polarity Mapping | ![]() Operations Bottleneck Analysis |
|---|---|---|---|
Purposedifferent | 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. | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 20-45 min | 1-2 h | 1-3 h |
Participantsdifferent | 3-12 | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | Polarity Map, Warning Signs, Balance Actions | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | LearningOperationsImprovement | Systems thinkingTradeoffsLeadership | FlowMeasurementConstraints |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






