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 Bottleneck Analysis | ![]() Operations After-Action Review | ![]() Operations Theory of Constraints |
|---|---|---|---|---|
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. | 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. | 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 system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-2 h | 1-3 h | 20-45 min | 2-4 h Analyse, laufend |
Participantsdifferent | 3-12 | 3-8 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Lessons learned, Action items, Event summary | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | Systems thinkingTradeoffsLeadership | FlowMeasurementConstraints | LearningOperationsImprovement | OperationsConstraintsFlowImprovement |



