View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  Systems Thinking Systems Mapping |  Architecture Architecture Decision Record |  Systems Thinking Intervention Mapping |
|---|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 1-2 Tage | 1-3 h | 15-45 min | 1-5 Tage |
Participantsdifferent | 1-4 | 3-12 | 1-3 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | System Map, Dependencies, Leverage Points | ADR File, Decision Log, Rationale | Logic Model, Change Objectives, Intervention Components, Evaluation Plan |
Tagsno overlap | ArchitectureDocumentationCommunication | Systems thinkingMappingBoundariesChange | ArchitectureRationaleDocumentationGovernance | ChangeSystems thinkingCapability |