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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Paper illustration of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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 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.When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions.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 min Setup, dann laufend30–60 min per interview1-3 TageSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-3 maintaining, briefing for everyone1 participant per interviewInternes TeamEvaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceInterview Notes, Themes, Insight SummaryPersona Profiles, Needs Summary, Scenario NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskTrackingStakeholdersGovernance
QualitativeResearchCustomerDiscovery
ResearchCustomerSynthesis
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods