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 two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible.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.
Complexitydifferent
LowMedium
Timedifferent
30–60 min per interview1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1 participant per interview3-20 Reviewer
Formatdifferent
Workshop + asyncAsync
Outputdifferent
Interview Notes, Themes, Insight SummaryRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
QualitativeResearchCustomerDiscovery
ArchitectureDecisionAsyncGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping