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 a horizontal story map with an activity backbone, task cards below it and a cross-map release line.
Product Discovery
User Story Mapping
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
Purposedifferent
When user goals and delivery scope could drift apart, it orders the journey from goal to slice. It makes visible where an MVP can genuinely be cut.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.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 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.
Complexitydifferent
MediumLowHighLow
Timedifferent
2-4 h1 h bis mehrere Wochen1-4 Wochen30-60 min
Participantsdifferent
4-101-81-61-5
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Story Map, Release Slices, Backlog CandidatesPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeExperiment results, Decision log, Learning summaryCompleted Experiment Canvas, Success Metric
Tagsno overlap
BacklogJourneyPlanningMVP
Continuous improvementLeanExperiments
ExperimentsGrowthAnalyticsValidation
ExperimentsValidationDiscoveryHypothesis
Add more methods