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 Pretotyping with its method-specific working model.
Product Discovery
Pretotyping
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowMediumHighMedium
Timedifferent
Stunden bis wenige Tage1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope1-4 h
Participantsdifferent
1-42-8Evaluation team, architects, and relevant stakeholders3-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Pretotyping sketch, Test setup, Conversion data, Go or no-go decisionCause Tree, Evidence Notes, CountermeasuresPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
ValidationDemandMVP
Root causeTreeIncidentQuality
ArchitectureQualityRiskTradeoffsStakeholders
Root causeProblem solvingQualityIncident
Add more methods