View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Domain Modeling Domain Context Map |  Systems Thinking Future Reality Tree |  Systems Thinking Evaporating Cloud |
|---|---|---|---|---|
Purposedifferent | 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. | 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 | Ongoing | 1-3 h | 2-4 h | 60-120 min |
Participantsdifferent | 2-12 | 3-10 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | 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 | FlowVisual managementDelivery | Domain-Driven DesignContextBoundaries | Theory of ConstraintsSystems thinkingChange | Theory of ConstraintsAssumptionsSystems thinking |