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 |  Decision Making Force Field Analysis |  Architecture Architecture Decision Record |  Decision Making OODA Loop |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-4 h | 45-90 min | 15-45 min | 15-60 min je Zyklus |
Participantsdifferent | 1-5 | 3-12 | 1-3 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Force Field Map, Change Levers, Risk Notes | ADR File, Decision Log, Rationale | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ArchitectureCommunicationVisualization | ChangeDecisionStrategy | ArchitectureRationaleDocumentationGovernance | DecisionChangeLearningStrategy |