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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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
MediumMediumLowLow
Timedifferent
2-4 h1-3 h30-120 min10-20 min daily
Participantsdifferent
4-103-102-61
Formatdifferent
WorkshopWorkshopWorkshopAsync
Outputdifferent
Story Map, Release Slices, Backlog CandidatesProcess Map, Handoff List, Improvement BacklogObservation Notes, Improvement IdeasDaily Plan, Time Estimates, Review Notes
Tagsno overlap
BacklogJourneyPlanningMVP
ProcessOperationsImprovement
LeanObservationProcessOperations
PlanningTime managementProductivityOperations
Add more methods