View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Delegation Poker | ![]() Agile Sailboat Retrospective | ![]() Operations Learning Review |
|---|---|---|---|
Purposedifferent | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 45-90 min | 45-90 min | 1-3 h |
Participantsdifferent | 3-10 | 4-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Sailboat Board, Risks, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | AutonomyRolesTeam | RetrospectiveTeamImprovement | LearningRetrospectiveIncidentOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






