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 C4 Model |  Architecture Architecture Decision Record |  Systems Thinking Intervention 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Medium | Low | Low | High |
Timedifferent | 1-3 h | 1-4 h | 15-45 min | 1-5 Tage |
Participantsdifferent | 3-12 | 1-5 | 1-3 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | Logic Model, Change Objectives, Intervention Components, Evaluation Plan |
Tagsno overlap | Systems thinkingMappingBoundariesChange | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | ChangeSystems thinkingCapability |