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 Change Analysis |  Domain Modeling Domain Context Map |  Systems Thinking Future Reality Tree |
|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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 | Medium | High |
Timedifferent | 45-120 min | 1-3 h | 2-4 h |
Participantsdifferent | 2-6 | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Domain Context Map, Boundary Notes, Ownership Map | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | Domain-Driven DesignContextBoundaries | Theory of ConstraintsSystems thinkingChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
