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 | ![]() Decision Making Decision Rights Mapping |
|---|---|---|---|
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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 h | 15-45 min | 90-180 min |
Participantsdifferent | 3-12 | 1-3 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | ADR File, Decision Log, Rationale | Decision Rights Matrix, Agreement |
Tagsno overlap | Systems thinkingMappingBoundariesChange | ArchitectureRationaleDocumentationGovernance | DecisionGovernanceAlignmentResponsibility |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






