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 Request for Comments |  Delivery RAID Log |  Decision Making Force Field Analysis |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend | 45-90 min |
Participantsdifferent | 3-20 Reviewer | 1-3 maintaining, briefing for everyone | 3-12 |
Formatdifferent | Async | Async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
