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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Purposedifferent
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.With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible.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 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.
Complexitydifferent
HighLowLowMedium
Timedifferent
Halber Tag45-90 min20-45 min90-180 min
Participantsdifferent
5-202-81-84-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksRACI Matrix, Responsibility Map, Decision NotesOwnership Reflection, Action Commitment, Coaching NotesDecision Rights Matrix, Agreement
Tagsno overlap
ResilienceOperationsIncident
RolesResponsibilityGovernanceOperations
ResponsibilityLeadershipTeam
DecisionGovernanceAlignmentResponsibility
Add more methods