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 Pretotyping with its method-specific working model.
Product Discovery
Pretotyping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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
LowLowHighHigh
Timedifferent
30 min Setup, dann laufendStunden bis wenige Tage1-4 WochenSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-3 maintaining, briefing for everyone1-41-6Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourcePretotyping sketch, Test setup, Conversion data, Go or no-go decisionExperiment results, Decision log, Learning summaryPrioritized 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
ValidationDemandMVP
ExperimentsGrowthAnalyticsValidation
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods