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 Argument Mapping |  Architecture Request for Comments |  Decision Making Force Field Analysis |  Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. | 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 30-60 min |
Participantsdifferent | 1-8 | 3-20 Reviewer | 3-12 | 2-10 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Argument Map, Evidence Gaps, Decision Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Force Field Map, Change Levers, Risk Notes | DACI Matrix, Decision Owner, Decision Log |
Tags1 shared | SensemakingDecisionRationale | ArchitectureDecisionAsyncGovernance | ChangeDecisionStrategy | DecisionRolesGovernanceAlignment |