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 of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.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.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 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.
Complexitydifferent
LowLowLowHigh
Timedifferent
30-60 min30 min Setup, dann laufend1-5 Tage1-4 Wochen
Participantsdifferent
2-61-3 maintaining, briefing for everyoneNutzertraffic1-6
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
Counter Metric List, Guardrail DefinitionsRAID Log, Status Report SourceInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
MetricsMeasurementStrategyExperiments
RiskTrackingStakeholdersGovernance
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods