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 |  DevOps Incident Timeline Analysis |  Agile Sailboat Retrospective |  Agile 4Ls 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. | For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h | 60-180 min | 45-90 min | 45–75 min |
Participantsdifferent | 3-12 | 3-10 | 4-12 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions | Sailboat Board, Risks, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Systems thinkingTradeoffsLeadership | IncidentTimelineSite Reliability Engineering | RetrospectiveTeamImprovement | RetrospectiveLearningReflectionTeam |