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 | ![]() Architecture Architecture Communication Canvas | ![]() Architecture Architecture Inception Canvas | ![]() Facilitation Alignment 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | 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 | High | Medium | Low | Medium |
Timedifferent | Halber Tag | 60-120 min | 1-2 h | 1-2 h |
Participantsdifferent | 5-20 | 2-8 | 3-8 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Inception Canvas, Risks, Goal List, Open Questions | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ResilienceOperationsIncident | ArchitectureCommunicationStakeholdersCanvas | AlignmentArchitectureCanvas | AlignmentStakeholdersStrategyFacilitation |



