View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling PARA Method |  Agile Starfish Retrospective |  Operations Root Cause Analysis |  Operations 5 Whys |
|---|---|---|---|---|
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 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h Setup, laufend | 45-90 min | 1-4 h | 15-30 min |
Participantsdifferent | 1 | 4-12 | 3-8 | 2-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Starfish Board, Practice Changes, Experiments | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | KnowledgeProductivityOrganization | RetrospectiveImprovementExperimentsTeam | Root causeProblem solvingQualityIncident | Root causeIncidentLeanProblem solving |