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 |  Domain Modeling Domain Context Map |  Systems Thinking Future Reality Tree |  Systems Thinking Evaporating Cloud |
|---|---|---|---|---|
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. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h | 1-3 h | 2-4 h | 60-120 min |
Participantsdifferent | 4-10 | 3-10 | 3-8 | 2-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Domain Context Map, Boundary Notes, Ownership Map | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | LeanFlowWasteDelivery | Domain-Driven DesignContextBoundaries | Theory of ConstraintsSystems thinkingChange | Theory of ConstraintsAssumptionsSystems thinking |