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 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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 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
MediumHighHighLow
Timedifferent
2-4 h1-6 Wochen2-8 h30-60 min
Participantsdifferent
4-104-102-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Story Map, Release Slices, Backlog Candidates8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanProblem Analysis, Decision Analysis, Risk PlanFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
BacklogJourneyPlanningMVP
QualityProblem solvingRoot cause
Problem solvingRoot causeDecisionOperations
Root causeQualityOperations
Add more methods