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 |  Operations Runbook |  Knowledge Modeling Knowledge Mapping |  Knowledge Modeling Concept 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | Halber Tag | 20-60 min | 1-3 h | 1-2 h |
Participantsdifferent | 5-20 | 1-4 | 3-12 | 1-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Runbook, Checklist, Escalation Path | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | ResilienceOperationsIncident | OperationsReliabilityDocumentation | KnowledgeMappingRisk | KnowledgeConceptsMappingSensemaking |