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 for NoEstimates.
Agile
NoEstimates
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
Purposedifferent
When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules.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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.
Complexitydifferent
MediumLowLowMedium
Timedifferent
laufend20–45 min1-5 Tage1-5 Tage
Participantsdifferent
2-12Small cross-functional groupNutzertrafficNutzertraffic
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Throughput Data, Flow Forecast, Slicing RulesRisk list, Mitigation plan, Assumption logInterest Metrics, Conversion Signal, Learning NoteClick Data, Interest Signal, Learning Decision
Tagsno overlap
EstimationForecastingFlow
RiskDecisionFailurePlanning
ValidationExperimentsDemandGrowth
ValidationExperimentsDemandDiscovery
Add more methods