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 Theory of Constraints | ![]() 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. | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits 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. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 1-3 h Setup, laufend | 2-4 h Analyse, laufend | 45-90 min |
Participantsdifferent | 1 | 3-12 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Constraint Map, Improvement Plan, Flow Metrics | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | KnowledgeProductivityOrganization | OperationsConstraintsFlowImprovement | RetrospectiveImprovementExperimentsTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






