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 | ![]() Systems Thinking Evaporating Cloud | ![]() Agile 4Ls Retrospective | ![]() Agile Mad Sad Glad |
|---|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h | 60-120 min | 45–75 min | 30-60 min |
Participantsdifferent | 3-12 | 2-8 | Team members involved | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | 4Ls Board, Learning Themes, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | Systems thinkingTradeoffsLeadership | Theory of ConstraintsAssumptionsSystems thinking | RetrospectiveLearningReflectionTeam | RetrospectiveTeamReflection |



