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 for RAPID
Decision Making
RAPID
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 of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Purposedifferent
In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.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 organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.
Complexitysame
MediumMediumMediumMedium
Timedifferent
45-90 min1-3 Wochen vom Draft bis zur Entscheidung1-3 h90-180 min
Participantsdifferent
3-123-20 Reviewer1-84-12
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
RAPID Role Map, Recommendation, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArgument Map, Evidence Gaps, Decision RationaleDecision Rights Matrix, Agreement
Tags1 shared
DecisionRolesGovernance
ArchitectureDecisionAsyncGovernance
SensemakingDecisionRationale
DecisionGovernanceAlignmentResponsibility
Add more methods