View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation TRIZ |  Architecture Architecture Decision Record |  Operations 5 Whys |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | 1-4 h | 15-45 min | 15-30 min | 1-4 h |
Participantsdifferent | 2-8 | 1-3 | 2-6 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Contradiction Statement, Inventive Principles, Solution Concepts | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | InnovationProblem solvingContradictionsCreativity | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |