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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Purposedifferent
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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.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
LowLowMedium
Timedifferent
20-60 min20-45 min1-2 h
Participantsdifferent
1-43-121-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathLessons learned, Action items, Event summaryConcept Map, Relationship Labels, Knowledge Gaps
Tagsno overlap
OperationsReliabilityDocumentation
LearningOperationsImprovement
KnowledgeConceptsMappingSensemaking
Add more methods

Often compared together

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

Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping