View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations ABC Analysis |  Operations Fishbone Diagram |  Agile Specification by Example |  Decision Making Pareto Analysis |
|---|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-60 min | 30-60 min | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 1-5 | 2-8 | 3-6 | 1-6 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | Fishbone Diagram, Cause Categories, Investigation Backlog | Example Table, Acceptance Tests | Pareto Chart, Top Causes, Focus List |
Tagsno overlap | PrioritizationOperationsPortfolio | Root causeQualityOperations | AgileRequirementsExamplesBehavior-Driven Development | PrioritizationQualityFocusRoot cause |