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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.
Complexitydifferent
LowLowMediumHigh
Timedifferent
30–60 min per interview20–45 min1-3 Wochen vom Draft bis zur EntscheidungSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1 participant per interviewSmall cross-functional group3-20 ReviewerEvaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Interview Notes, Themes, Insight SummaryRisk list, Mitigation plan, Assumption logRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
QualitativeResearchCustomerDiscovery
RiskDecisionFailurePlanning
ArchitectureDecisionAsyncGovernance
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods