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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
Paper illustration for Responsibility Poker.
Facilitation
Responsibility Poker
Purposedifferent
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.When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences.
Complexitysame
LowLowLow
Timedifferent
20-60 min20-45 min45-90 min
Participantsdifferent
1-41-83-10
Formatdifferent
AsyncWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathOwnership Reflection, Action Commitment, Coaching NotesResponsibility Map, Role Agreements, Open Questions
Tagsno overlap
OperationsReliabilityDocumentation
ResponsibilityLeadershipTeam
RolesResponsibilityTeamFacilitation
Add more methods

Often compared together

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

Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for 1-2-4-All.
Facilitation
1-2-4-All