View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Accountability Ladder | ![]() Systems Thinking Polarity Mapping | ![]() Agile Sailboat Retrospective | ![]() Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | 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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20-45 min | 1-2 h | 45-90 min | 45-90 min |
Participantsdifferent | 1-8 | 3-12 | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Ownership Reflection, Action Commitment, Coaching Notes | Polarity Map, Warning Signs, Balance Actions | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ResponsibilityLeadershipTeam | Systems thinkingTradeoffsLeadership | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |



