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 | ![]() Operations Ivy Lee Method | ![]() Operations Theory of Constraints |
|---|---|---|---|---|
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. | With a restless workday full of too many open items, the method creates radical simplicity. It directs attention to a short sequence instead of a broad, still-open field. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 h Setup, laufend | 1-3 h | 5-10 min daily | 2-4 h Analyse, laufend |
Participantsdifferent | 1 | 3-8 | 1 | 3-12 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Daily Priority List, Completion Notes | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | KnowledgeProductivityOrganization | FlowMeasurementConstraints | PrioritizationProductivityExecution | OperationsConstraintsFlowImprovement |



