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 of a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
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 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-2 h45-90 min30-60 min45-90 min
Participantsdifferent
3-123-103-124-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsDelegation Board, Decision Boundaries, Role AgreementsStart Stop Continue Board, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
Systems thinkingTradeoffsLeadership
AutonomyRolesTeam
RetrospectiveImprovementTeamReflection
RetrospectiveTeamImprovement
Add more methods