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 |  Domain Modeling Domain Context Map |  Operations Bottleneck Analysis |  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. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. | 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 | Medium | High |
Timedifferent | 1-3 h Setup, laufend | 1-3 h | 1-3 h | 2-4 h Analyse, laufend |
Participantsdifferent | 1 | 3-10 | 3-8 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Domain Context Map, Boundary Notes, Ownership Map | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | KnowledgeProductivityOrganization | Domain-Driven DesignContextBoundaries | FlowMeasurementConstraints | OperationsConstraintsFlowImprovement |