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.

Selected:Card SortingRAID LogFishbone DiagramATAM (Architecture Tradeoff Analysis Method)
Criterion
Paper illustration showing three sorted card stacks and an open question about a possible group.
UX Research
Card Sorting
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations.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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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
LowLowLowHigh
Timedifferent
20-45 min30 min Setup, dann laufend30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
Based on research question1-3 maintaining, briefing for everyone2-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Content groups, Label set, IA hypothesesRAID Log, Status Report SourceFishbone Diagram, Cause Categories, Investigation BacklogPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Information architectureNavigationStructure
RiskTrackingStakeholdersGovernance
Root causeQualityOperations
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods