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 Causal Factor Analysis.
Operations
Causal Factor Analysis
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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 event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.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.
Complexitydifferent
MediumHighHighMedium
Timedifferent
2-4 h2-6 h2-8 h1-4 h
Participantsdifferent
4-103-102-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Story Map, Release Slices, Backlog CandidatesEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsProblem Analysis, Decision Analysis, Risk PlanProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
BacklogJourneyPlanningMVP
CausalityIncidentRoot causeTimeline
Problem solvingRoot causeDecisionOperations
Root causeProblem solvingQualityIncident
Add more methods