View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Systems Mapping |  Architecture Architecture Decision Record |  Operations Change Analysis |  Systems Thinking Future Reality Tree |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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 | Low | Medium | High |
Timedifferent | 1-3 h | 15-45 min | 45-120 min | 2-4 h |
Participantsdifferent | 3-12 | 1-3 | 2-6 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | ADR File, Decision Log, Rationale | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | Systems thinkingMappingBoundariesChange | ArchitectureRationaleDocumentationGovernance | ChangeRoot causeTroubleshootingComparison | Theory of ConstraintsSystems thinkingChange |