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
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Starfish Retrospective
Agile
Starfish 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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.
Complexitydifferent
MediumLowLow
Timedifferent
1-3 h Setup, laufend30-60 min45-90 min
Participantsdifferent
12-84-12
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveFishbone Diagram, Cause Categories, Investigation BacklogStarfish Board, Practice Changes, Experiments
Tagsno overlap
KnowledgeProductivityOrganization
Root causeQualityOperations
RetrospectiveImprovementExperimentsTeam
Add more methods

Often compared together

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

Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective