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 yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Purposedifferent
When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
LowLowHighMedium
Timedifferent
30-60 min15-30 min1-6 Wochen1-3 h
Participantsdifferent
3-72-64-102-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsRoot cause notes, Countermeasures8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Root causeIncidentLeanProblem solving
QualityProblem solvingRoot cause
Root causeTreeIncidentQuality
Add more methods