methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.
Complexitydifferent
HighLowLow
Timedifferent
Halber Tag1-2 Tage20-60 min
Participantsdifferent
5-201-41-4
Formatdifferent
WorkshopWorkshop + asyncAsync
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksArchitecture Document, Context View, Runtime View, Deployment ViewRunbook, Checklist, Escalation Path
Tagsno overlap
ResilienceOperationsIncident
ArchitectureDocumentationCommunication
OperationsReliabilityDocumentation
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem