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 ALPEN Method | ![]() Operations Theory of Constraints | ![]() Operations Bottleneck Analysis |
|---|---|---|---|---|
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. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. | 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. | 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. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-2 h | 10-20 min daily | 2-4 h Analyse, laufend | 1-3 h |
Participantsdifferent | 1-8 | 1 | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Daily Plan, Time Estimates, Review Notes | Constraint Map, Improvement Plan, Flow Metrics | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | PlanningTime managementProductivityOperations | OperationsConstraintsFlowImprovement | FlowMeasurementConstraints |



