View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Change Analysis |  Architecture Architecture Decision Record |  Decision Making Force Field Analysis |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 45-120 min | 15-45 min | 45-90 min | 1-2 Tage |
Participantsdifferent | 2-6 | 1-3 | 3-12 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | ADR File, Decision Log, Rationale | Force Field Map, Change Levers, Risk Notes | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | ArchitectureRationaleDocumentationGovernance | ChangeDecisionStrategy | ArchitectureDocumentationCommunication |