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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Paper illustration for ALPEN Method
Operations
ALPEN Method
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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.
Complexitydifferent
MediumLowMediumLow
Timedifferent
2-4 h1 h bis mehrere Wochen45-90 min10-20 min daily
Participantsdifferent
4-101-82-51
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Story Map, Release Slices, Backlog CandidatesPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeA3 Report, Action Plan, Root Cause AnalysisDaily Plan, Time Estimates, Review Notes
Tagsno overlap
BacklogJourneyPlanningMVP
Continuous improvementLeanExperiments
LeanProblem solvingCoachingOperations
PlanningTime managementProductivityOperations
Add more methods