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 | ![]() Engineering Kanban | ![]() Systems Thinking Current Reality Tree | ![]() Systems Thinking Theory of Constraints Thinking Process |
|---|---|---|---|---|
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. | 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. | A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once. | The Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship. |
Complexitydifferent | Low | Medium | High | High |
Timedifferent | Ongoing | Ongoing | 2-6 h | 0.5-3 Tage |
Participantsdifferent | 1-20 | 2-12 | 3-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | Kanban board, WIP policies, Flow metrics | Current Reality Tree, Core Problems, Intervention Ideas | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles |
Tagsno overlap | SignalsOperationsVisual management | FlowVisual managementDelivery | Systems thinkingRoot causeConstraintsCausality | Theory of ConstraintsConstraintsSystems thinkingCausality |



