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 |  Delivery RAID Log |  Architecture Request for Comments |
|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-20 Reviewer |
Formatdifferent | Workshop | Async | Async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | RAID Log, Status Report Source | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ChangeDecisionStrategy | RiskTrackingStakeholdersGovernance | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
