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 |  Team Design Team Cognitive Load Assessment |  Facilitation Responsibility Poker |  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 juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list. | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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 | Medium | Low | Low |
Timedifferent | 1-2 h | 60-90 min | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 3-12 | 3-10 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Cognitive Load Profile, Action List | Responsibility Map, Role Agreements, Open Questions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | Systems thinkingTradeoffsLeadership | TeamComplexityImprovementDiagnosis | RolesResponsibilityTeamFacilitation | RetrospectiveTeamImprovement |