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 paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.
Complexitydifferent
LowMediumLowLow
Timedifferent
20–45 min2-6 h1-5 Tage45-90 min
Participantsdifferent
Small cross-functional group2-8Nutzertraffic2-8
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logEvent Model, UI Flow, Commands, Read ModelsInterest Metrics, Conversion Signal, Learning NoteAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
RiskDecisionFailurePlanning
EventsBlueprintDomain-Driven DesignBehavior
ValidationExperimentsDemandGrowth
AssumptionsRiskDecisionDiscovery
Add more methods