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 Concept Mapping |  Operations Theory of Constraints |  Operations Learning Review |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | 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 | Medium | High | Medium | Low |
Timedifferent | 1-2 h | 2-4 h Analyse, laufend | 1-3 h | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 1-8 | 3-12 | 3-10 | Scrum Team |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Constraint Map, Improvement Plan, Flow Metrics | Learning Review Notes, System Factors, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | OperationsConstraintsFlowImprovement | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementLearning |