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 C4 Model | ![]() Architecture arc42 | ![]() Decision Making OODA Loop | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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 | Low | Medium | Low |
Timedifferent | 1-4 h | 1-2 Tage | 15-60 min je Zyklus | 45-90 min |
Participantsdifferent | 1-5 | 1-4 | 1-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View | Situation Assessment, Decision Loop, Action Updates | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication | DecisionChangeLearningStrategy | ChangeDecisionStrategy |



