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 arc42 with its core stages and visible working result.
Architecture
arc42
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.
Complexitydifferent
LowLowHighLow
Timedifferent
20–45 min1-2 Tage1-4 Wochen1-5 Tage
Participantsdifferent
Small cross-functional group1-41-6Nutzertraffic
Formatdifferent
WorkshopWorkshop + asyncAsyncAsync
Outputdifferent
Risk list, Mitigation plan, Assumption logArchitecture Document, Context View, Runtime View, Deployment ViewExperiment results, Decision log, Learning summaryInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
RiskDecisionFailurePlanning
ArchitectureDocumentationCommunication
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandGrowth
Add more methods