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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Concierge MVP
Product Discovery
Concierge MVP
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Purposedifferent
In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
LowHighMediumMedium
Timedifferent
20–45 min1-4 Wochen1-4 Wochen45-60 min
Participantsdifferent
Small cross-functional group1-63-10 Kunden2-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logExperiment results, Decision log, Learning summaryConcierge Learnings, Service Blueprint, MVP RisksAssumption map, Test backlog, Risk ranking
Tagsno overlap
RiskDecisionFailurePlanning
ExperimentsGrowthAnalyticsValidation
MVPValidationServiceDiscovery
AssumptionsRiskExperimentsValidation
Add more methods