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 Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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.
Complexitydifferent
LowHighMediumLow
Timedifferent
20-45 minHalber Tag1-2 h45-90 min
Participantsdifferent
1-85-204-123-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Ownership Reflection, Action Commitment, Coaching NotesSimulation Notes, Gaps List, Updated RunbooksAlignment Map, Open Issues, Decision QuestionsExpectation Map, Alignment Notes, Agreements
Tagsno overlap
ResponsibilityLeadershipTeam
ResilienceOperationsIncident
AlignmentStakeholdersStrategyFacilitation
AlignmentStakeholdersTeam
Add more methods