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 Bottleneck Analysis |  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 a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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 | Medium | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 1-3 h | 45-90 min | 45–75 min |
Participantsdifferent | 1 | 3-8 | 4-12 | Team members involved |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | KnowledgeProductivityOrganization | FlowMeasurementConstraints | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |