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 Accountability Ladder
Operations
Accountability Ladder
Paper illustration of a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
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
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.Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min20-45 min1-2 h45–75 min
Participantsdifferent
3-101-83-12Team members involved
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsOwnership Reflection, Action Commitment, Coaching NotesPolarity Map, Warning Signs, Balance Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
AutonomyRolesTeam
ResponsibilityLeadershipTeam
Systems thinkingTradeoffsLeadership
RetrospectiveLearningReflectionTeam
Add more methods