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 Expectation Mapping.
Facilitation
Expectation Mapping
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Purposedifferent
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 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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.
Complexitydifferent
LowHighLow
Timedifferent
45-90 minHalber Tag30-120 min
Participantsdifferent
3-125-202-6
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Expectation Map, Alignment Notes, AgreementsSimulation Notes, Gaps List, Updated RunbooksObservation Notes, Improvement Ideas
Tagsno overlap
AlignmentStakeholdersTeam
ResilienceOperationsIncident
LeanObservationProcessOperations
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command