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 Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
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.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.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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.
Complexitydifferent
HighMediumLowLow
Timedifferent
Halber Tag90-180 min45-90 min45-90 min
Participantsdifferent
5-204-123-122-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksDecision Rights Matrix, AgreementExpectation Map, Alignment Notes, AgreementsRACI Matrix, Responsibility Map, Decision Notes
Tagsno overlap
ResilienceOperationsIncident
DecisionGovernanceAlignmentResponsibility
AlignmentStakeholdersTeam
RolesResponsibilityGovernanceOperations
Add more methods