View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Theory of Constraints |  Domain Modeling Context Map |  Operations Learning Review |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | 2-4 h Analyse, laufend | 1-3 h | 1-3 h | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-12 | 2-8 | 3-10 | Scrum Team |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Context Map, Integration Patterns, Boundary Notes | Learning Review Notes, System Factors, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | OperationsConstraintsFlowImprovement | Domain-Driven DesignBoundariesStrategy | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementLearning |