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 Analysis.
Operations
Root Cause Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects 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.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.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
LowMediumHighHigh
Timedifferent
Stunden bis wenige Tage1-4 hSeveral meetings plus preparation and analysis; total effort depends on scope2-6 h
Participantsdifferent
1-43-8Evaluation team, architects, and relevant stakeholders3-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Pretotyping sketch, Test setup, Conversion data, Go or no-go decisionProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ValidationDemandMVP
Root causeProblem solvingQualityIncident
ArchitectureQualityRiskTradeoffsStakeholders
RiskQualityOperationsRoot cause
Add more methods