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 Delegation Poker.
Facilitation
Delegation Poker
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
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's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.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 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 min30-60 min45-90 min45-90 min
Participantsdifferent
3-103-104-124-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsEmotion Board, Themes, Action ItemsStarfish Board, Practice Changes, ExperimentsSailboat Board, Risks, Improvement Actions
Tags1 shared
AutonomyRolesTeam
RetrospectiveTeamReflection
RetrospectiveImprovementExperimentsTeam
RetrospectiveTeamImprovement
Add more methods