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 |  Agile Sailboat Retrospective |  Operations Learning Review |  Operations After-Action Review |
|---|---|---|---|---|
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. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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 | Low | Medium | Low |
Timedifferent | 1-2 h | 45-90 min | 1-3 h | 20-45 min |
Participantsdifferent | 3-12 | 4-12 | 3-10 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Sailboat Board, Risks, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RetrospectiveTeamImprovement | LearningRetrospectiveIncidentOperations | LearningOperationsImprovement |