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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
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.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.
Complexitydifferent
MediumLowLow
Timedifferent
1-2 h20-60 min20-45 min
Participantsdifferent
3-121-41-8
Formatdifferent
WorkshopAsyncWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsRunbook, Checklist, Escalation PathOwnership Reflection, Action Commitment, Coaching Notes
Tagsno overlap
Systems thinkingTradeoffsLeadership
OperationsReliabilityDocumentation
ResponsibilityLeadershipTeam
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
Paper illustration for Responsibility Poker.
Facilitation
Responsibility 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