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 Leverage Points |  Architecture C4 Model |  Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 1-2 Tage | Half day | 1-4 h | 45-90 min |
Participantsdifferent | 1-4 | 3-12 | 1-5 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Leverage Map, Action Strategy | Context Diagram, Container Diagram, Component Diagram | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureDocumentationCommunication | Systems thinkingChangeStrategy | ArchitectureCommunicationVisualization | ChangeDecisionStrategy |