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 |  DevOps Game Day |  Facilitation Stakeholder Mapping |  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. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | High | Low | Medium |
Timedifferent | 45-90 min | Halber Tag | 60–90 min | 1-2 h |
Participantsdifferent | 3-12 | 5-20 | 2-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Simulation Notes, Gaps List, Updated Runbooks | Stakeholder Map, Engagement Plan, Risk Notes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | AlignmentStakeholdersTeam | ResilienceOperationsIncident | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersStrategyFacilitation |