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
Four paper collections for projects, responsibilities, resources and archives.
Knowledge Modeling
PARA Method
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Purposedifferent
The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work.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.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.
Complexitydifferent
MediumLowHigh
Timedifferent
1-3 h Setup, laufend20-60 minHalber Tag
Participantsdifferent
11-45-20
Formatdifferent
AsyncAsyncWorkshop
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveRunbook, Checklist, Escalation PathSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
KnowledgeProductivityOrganization
OperationsReliabilityDocumentation
ResilienceOperationsIncident
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
Paper illustration for ALPEN Method
Operations
ALPEN Method
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Learning Review.
Operations
Learning Review