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
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
2-4 h1-3 h1-4 h30-60 min
Participantsdifferent
4-103-103-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Story Map, Release Slices, Backlog CandidatesProcess Map, Handoff List, Improvement BacklogProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
BacklogJourneyPlanningMVP
ProcessOperationsImprovement
Root causeProblem solvingQualityIncident
Root causeQualityOperations
Add more methods