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 team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h Setup, laufend20-60 min30-60 min45-90 min
Participantsdifferent
11-43-124-12
Formatdifferent
AsyncAsyncWorkshopWorkshop
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveRunbook, Checklist, Escalation PathStart Stop Continue Board, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
KnowledgeProductivityOrganization
OperationsReliabilityDocumentation
RetrospectiveImprovementTeamReflection
RetrospectiveTeamImprovement
Add more methods