View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Operations Root Cause Analysis | ![]() Innovation TRIZ |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 15-45 min | 1-4 h | 1-4 h |
Participantsdifferent | 1-3 | 3-8 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Contradiction Statement, Inventive Principles, Solution Concepts |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Root causeProblem solvingQualityIncident | InnovationProblem solvingContradictionsCreativity |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






