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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Hypothesis Prioritization Canvas with a method-specific labelled workspace.
Product Discovery
Hypothesis Prioritization Canvas
Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
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.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 many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog.When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric.
Complexitydifferent
LowHighMediumLow
Timedifferent
Stunden bis wenige TageSeveral meetings plus preparation and analysis; total effort depends on scope60-90 min30-60 min
Participantsdifferent
1-4Evaluation team, architects, and relevant stakeholders3-81-5
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Pretotyping sketch, Test setup, Conversion data, Go or no-go decisionPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPrioritization Canvas, Hypothesis BacklogCompleted Experiment Canvas, Success Metric
Tagsno overlap
ValidationDemandMVP
ArchitectureQualityRiskTradeoffsStakeholders
ExperimentsPrioritizationDiscoveryHypothesis
ExperimentsValidationDiscoveryHypothesis
Add more methods