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 for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
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.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.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
LowHighLowMedium
Timedifferent
20-45 minHalber Tag45-90 min90-180 min
Participantsdifferent
1-85-203-124-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Ownership Reflection, Action Commitment, Coaching NotesSimulation Notes, Gaps List, Updated RunbooksExpectation Map, Alignment Notes, AgreementsDecision Rights Matrix, Agreement
Tagsno overlap
ResponsibilityLeadershipTeam
ResilienceOperationsIncident
AlignmentStakeholdersTeam
DecisionGovernanceAlignmentResponsibility
Add more methods