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 |  Architecture Request for Comments |  Delivery RAID Log |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend | 1-2 h |
Participantsdifferent | 3-12 | 3-20 Reviewer | 1-3 maintaining, briefing for everyone | 4-12 |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ChangeDecisionStrategy | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersStrategyFacilitation |