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
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
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.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.
Complexitydifferent
MediumLowLow
Timedifferent
1-3 h Setup, laufend20-60 min20-45 min
Participantsdifferent
11-43-12
Formatdifferent
AsyncAsyncWorkshop + async
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveRunbook, Checklist, Escalation PathLessons learned, Action items, Event summary
Tagsno overlap
KnowledgeProductivityOrganization
OperationsReliabilityDocumentation
LearningOperationsImprovement
Add more methods

Often compared together

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

Paper illustration for ALPEN Method
Operations
ALPEN Method
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