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 4Ls Retrospective |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  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. | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 | Low | High | Low |
Timedifferent | 1-2 h | 45–75 min | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 3-12 | Team members involved | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | 4Ls Board, Learning Themes, Improvement Actions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Emotion Board, Themes, Action Items |
Tagsno overlap | Systems thinkingTradeoffsLeadership | RetrospectiveLearningReflectionTeam | ArchitectureQualityRiskTradeoffsStakeholders | RetrospectiveTeamReflection |