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 |  Domain Modeling Bounded Context Canvas |  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. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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 | 1-3 h | 2-4 h |
Participantsdifferent | 3-12 | 1-3 | 3-8 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | ADR File, Decision Log, Rationale | Context Canvas, Glossary, Integration Notes | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | Systems thinkingMappingBoundariesChange | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignBoundariesModeling | Theory of ConstraintsSystems thinkingChange |