View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Three Amigos |  Operations Root Cause Analysis |  Innovation TRIZ |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 15-30 min | 1-4 h | 1-4 h | 15-30 min |
Participantsdifferent | 3 | 3-8 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Contradiction Statement, Inventive Principles, Solution Concepts | Root cause notes, Countermeasures |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | Root causeProblem solvingQualityIncident | InnovationProblem solvingContradictionsCreativity | Root causeIncidentLeanProblem solving |