View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Force Field Analysis |  Operations Change Analysis |  Architecture Request for Comments |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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 RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 45-120 min | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min |
Participantsdifferent | 3-12 | 2-6 | 3-20 Reviewer | 1-3 |
Formatdifferent | Workshop | Workshop + async | Async | Async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale |
Tagsno overlap | ChangeDecisionStrategy | ChangeRoot causeTroubleshootingComparison | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance |