View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Game Day |  Facilitation Alignment Mapping |  Facilitation Responsibility Poker |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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 | High | Medium | Low | Low |
Timedifferent | Halber Tag | 1-2 h | 45-90 min | 45-90 min |
Participantsdifferent | 5-20 | 4-12 | 3-10 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Alignment Map, Open Issues, Decision Questions | Responsibility Map, Role Agreements, Open Questions | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | ResilienceOperationsIncident | AlignmentStakeholdersStrategyFacilitation | RolesResponsibilityTeamFacilitation | AlignmentStakeholdersTeam |