View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Polarity Mapping |  Operations After-Action Review |  Operations Bottleneck Analysis |  Operations Process Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 h | 20-45 min | 1-3 h | 1-3 h |
Participantsdifferent | 3-12 | 3-12 | 3-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Lessons learned, Action items, Event summary | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | Systems thinkingTradeoffsLeadership | LearningOperationsImprovement | FlowMeasurementConstraints | ProcessOperationsImprovement |