View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Value Stream Mapping |  Systems Thinking Intervention Mapping |  Domain Modeling Domain Context Map |  Systems Thinking Future Reality Tree |
|---|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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 Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 1-3 h | 1-5 Tage | 1-3 h | 2-4 h |
Participantsdifferent | 4-10 | 4-12 | 3-10 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Domain Context Map, Boundary Notes, Ownership Map | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | LeanFlowWasteDelivery | ChangeSystems thinkingCapability | Domain-Driven DesignContextBoundaries | Theory of ConstraintsSystems thinkingChange |