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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge 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.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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.
Complexitydifferent
HighLowMedium
Timedifferent
Halber Tag20-60 min1-3 h
Participantsdifferent
5-201-43-12
Formatdifferent
WorkshopAsyncWorkshop
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksRunbook, Checklist, Escalation PathKnowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap
ResilienceOperationsIncident
OperationsReliabilityDocumentation
KnowledgeMappingRisk
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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis