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/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
Purposedifferent
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.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
HighLowLowMedium
Timedifferent
1-4 Wochen30 min Setup, dann laufend45-90 min1-5 Tage
Participantsdifferent
1-61-3 maintaining, briefing for everyone2-8Nutzertraffic
Formatdifferent
AsyncAsyncWorkshop + asyncAsync
Outputdifferent
Experiment results, Decision log, Learning summaryRAID Log, Status Report SourceAssumption List, Critical Assumptions, Learning PlanClick Data, Interest Signal, Learning Decision
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
RiskTrackingStakeholdersGovernance
AssumptionsRiskDecisionDiscovery
ValidationExperimentsDemandDiscovery
Add more methods