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 Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
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.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.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.
Complexitysame
LowLowLowLow
Timedifferent
45-90 min45-90 min20-45 min45-90 min
Participantsdifferent
4-123-101-84-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Starfish Board, Practice Changes, ExperimentsDelegation Board, Decision Boundaries, Role AgreementsOwnership Reflection, Action Commitment, Coaching NotesSailboat Board, Risks, Improvement Actions
Tags1 shared
RetrospectiveImprovementExperimentsTeam
AutonomyRolesTeam
ResponsibilityLeadershipTeam
RetrospectiveTeamImprovement
Add more methods