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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.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.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.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung0.5-3 Tage45-90 min1-3 h
Participantsdifferent
3-20 Reviewer5-153-121-8
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRich Picture, Root Definitions, Conceptual Models, Change AgendaRAPID Role Map, Recommendation, Decision LogArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
ArchitectureDecisionAsyncGovernance
Soft systemsComplexitySensemakingSystems thinking
DecisionRolesGovernance
SensemakingDecisionRationale
Add more methods