View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Force Field AnalysisChange AnalysisArchitecture Decision RecordSAAM (Software Architecture Analysis Method)
| Criterion |  Decision Making Force Field Analysis |  Operations Change Analysis |  Architecture Architecture Decision Record |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 45-90 min | 45-120 min | 15-45 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-12 | 2-6 | 1-3 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List | ADR File, Decision Log, Rationale | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives |
Tagsno overlap | ChangeDecisionStrategy | ChangeRoot causeTroubleshootingComparison | ArchitectureRationaleDocumentationGovernance | ArchitectureChangeAnalysisComparisonQuality |