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 Architecture Decision Record | ![]() Operations Change Analysis | ![]() Decision Making Force Field Analysis |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | Low |
Timedifferent | 15-45 min | 45-120 min | 45-90 min |
Participantsdifferent | 1-3 | 2-6 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ChangeRoot causeTroubleshootingComparison | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






