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 Intervention Mapping | ![]() Systems Thinking Future Reality Tree | ![]() Architecture arc42 | ![]() Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | High | High | Low | Low |
Timedifferent | 1-5 Tage | 2-4 h | 1-2 Tage | 1-4 h |
Participantsdifferent | 4-12 | 3-8 | 1-4 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ChangeSystems thinkingCapability | Theory of ConstraintsSystems thinkingChange | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization |



