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 Visual Management |  Operations Process Mapping |  Operations Theory of Constraints |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | Ongoing | 1-3 h | 2-4 h Analyse, laufend | Ongoing |
Participantsdifferent | 1-20 | 3-10 | 3-12 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | Process Map, Handoff List, Improvement Backlog | Constraint Map, Improvement Plan, Flow Metrics | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | SignalsOperationsVisual management | ProcessOperationsImprovement | OperationsConstraintsFlowImprovement | FlowVisual managementDelivery |