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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Opportunity Interview
Product Discovery
Opportunity Interview
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities.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 interview30 min Setup, dann laufend30-60 min je InterviewSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1 participant per interview1-3 maintaining, briefing for everyone5-12 InterviewsEvaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Interview Notes, Themes, Insight SummaryRAID Log, Status Report SourceInterview Notes, Opportunity Themes, Customer QuotesPrioritized 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
RiskTrackingStakeholdersGovernance
DiscoveryInterviewsOpportunityCustomer
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods