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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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
Purposedifferent
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.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.
Complexitysame
LowLow
Timedifferent
15-30 min30-60 min
Participantsdifferent
2-63-7
Formatsame
WorkshopWorkshop
Outputdifferent
Root cause notes, CountermeasuresExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
Root causeIncidentLeanProblem solving
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving