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 Accountability Ladder
Operations
Accountability Ladder
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.
Complexitydifferent
LowHighMediumMedium
Timedifferent
20-45 minHalber Tag90-180 minAs needed
Participantsdifferent
1-85-204-124-15
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Ownership Reflection, Action Commitment, Coaching NotesSimulation Notes, Gaps List, Updated RunbooksDecision Rights Matrix, AgreementIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
ResponsibilityLeadershipTeam
ResilienceOperationsIncident
DecisionGovernanceAlignmentResponsibility
IncidentOperationsReliability
Add more methods