View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team Cognitive Load AssessmentResponsibility PokerSailboat RetrospectiveStart Stop Continue
| Criterion |  Team Design Team Cognitive Load Assessment |  Facilitation Responsibility Poker |  Agile Sailboat Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-90 min | 45-90 min | 45-90 min | 30-60 min |
Participantsdifferent | 3-12 | 3-10 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Cognitive Load Profile, Action List | Responsibility Map, Role Agreements, Open Questions | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tags1 shared | TeamComplexityImprovementDiagnosis | RolesResponsibilityTeamFacilitation | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection |