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 |  Operations Runbook |  Agile Starfish Retrospective |  Agile 4Ls 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 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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 20-60 min | 45-90 min | 45–75 min |
Participantsdifferent | 1 | 1-4 | 4-12 | Team members involved |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Runbook, Checklist, Escalation Path | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | KnowledgeProductivityOrganization | OperationsReliabilityDocumentation | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |