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 |  Delivery Communication Plan |  Architecture Architecture Communication Canvas |
|---|---|---|---|
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 many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | High | Low | Medium |
Timedifferent | Halber Tag | 45-90 min | 60-120 min |
Participantsdifferent | 5-20 | 2-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Communication Plan, Channel Matrix, Message Cadence | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ResilienceOperationsIncident | CommunicationStakeholdersDeliveryPlanning | ArchitectureCommunicationStakeholdersCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
