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 Bottleneck Analysis |  Systems Thinking Systems Mapping |  Domain Modeling Domain Context Map |  Systems Thinking Current Reality Tree |
|---|---|---|---|---|
Purposedifferent | 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. | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 1-3 h | 1-3 h | 2-6 h |
Participantsdifferent | 3-8 | 3-12 | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | System Map, Dependencies, Leverage Points | Domain Context Map, Boundary Notes, Ownership Map | Current Reality Tree, Core Problems, Intervention Ideas |
Tagsno overlap | FlowMeasurementConstraints | Systems thinkingMappingBoundariesChange | Domain-Driven DesignContextBoundaries | Systems thinkingRoot causeConstraintsCausality |