methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls 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.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 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 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.
Complexitysame
LowLowLowLow
Timedifferent
20-45 min45-90 min45-90 min45–75 min
Participantsdifferent
1-84-123-10Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Ownership Reflection, Action Commitment, Coaching NotesSailboat Board, Risks, Improvement ActionsDelegation Board, Decision Boundaries, Role Agreements4Ls Board, Learning Themes, Improvement Actions
Tags1 shared
ResponsibilityLeadershipTeam
RetrospectiveTeamImprovement
AutonomyRolesTeam
RetrospectiveLearningReflectionTeam
Add more methods