View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Operations A3 Problem Solving |  DevOps Game Day |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 45-90 min | 45-90 min | Halber Tag | 1-2 h |
Participantsdifferent | 3-12 | 2-5 | 5-20 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | A3 Report, Action Plan, Root Cause Analysis | Simulation Notes, Gaps List, Updated Runbooks | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | AlignmentStakeholdersTeam | LeanProblem solvingCoachingOperations | ResilienceOperationsIncident | AlignmentStakeholdersStrategyFacilitation |