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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Flywheel.
Growth
Flywheel
Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric.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
LowMediumLowHigh
Timedifferent
30 min Setup, dann laufend60-120 min30-60 min1-4 Wochen
Participantsdifferent
1-3 maintaining, briefing for everyone3-81-51-6
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
RAID Log, Status Report SourceFlywheel Map, Friction Points, Growth Levers, Experiment BacklogCompleted Experiment Canvas, Success MetricExperiment results, Decision log, Learning summary
Tagsno overlap
RiskTrackingStakeholdersGovernance
GrowthRetentionConversion
ExperimentsValidationDiscoveryHypothesis
ExperimentsGrowthAnalyticsValidation
Add more methods