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
Empathy Mapping
UX Research
Empathy Mapping
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Affinity Diagramming
UX Research
Affinity Diagramming
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.When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.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.When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung30–60 min1-3 h45–90 min
Participantsdifferent
3-20 Reviewer4-81-83-10
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsEmpathy Map, Assumptions List, Research GapsArgument Map, Evidence Gaps, Decision RationaleTheme clusters, Insight statements, Opportunity areas
Tagsno overlap
ArchitectureDecisionAsyncGovernance
SynthesisQualitativeWorkshop
SensemakingDecisionRationale
SynthesisQualitativeRoot cause
Add more methods