methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for DACI
Decision Making
DACI
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.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.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
LowMediumMediumLow
Timedifferent
45-90 min1-3 Wochen vom Draft bis zur Entscheidung1-3 h30-60 min
Participantsdifferent
3-123-20 Reviewer1-82-10
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Force Field Map, Change Levers, Risk NotesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArgument Map, Evidence Gaps, Decision RationaleDACI Matrix, Decision Owner, Decision Log
Tags1 shared
ChangeDecisionStrategy
ArchitectureDecisionAsyncGovernance
SensemakingDecisionRationale
DecisionRolesGovernanceAlignment
Add more methods