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 for Concierge MVP
Product Discovery
Concierge MVP
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 an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution.
Complexitydifferent
MediumLowHighMedium
Timedifferent
2-4 h1 h bis mehrere Wochen1-4 Wochen1-4 Wochen
Participantsdifferent
4-101-81-63-10 Kunden
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Story Map, Release Slices, Backlog CandidatesPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeExperiment results, Decision log, Learning summaryConcierge Learnings, Service Blueprint, MVP Risks
Tagsno overlap
BacklogJourneyPlanningMVP
Continuous improvementLeanExperiments
ExperimentsGrowthAnalyticsValidation
MVPValidationServiceDiscovery
Add more methods