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 Start Stop Continue |  Operations Learning Review |  Agile Sailboat Retrospective |
|---|---|---|---|---|
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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 h | 30-60 min | 1-3 h | 45-90 min |
Participantsdifferent | 3-12 | 3-12 | 3-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Start Stop Continue Board, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RetrospectiveImprovementTeamReflection | LearningRetrospectiveIncidentOperations | RetrospectiveTeamImprovement |