View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordCompetency QuestionsRoot Cause AnalysisRoot Cause Tree Analysis
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Knowledge Modeling Competency Questions | ![]() Operations Root Cause Analysis | ![]() Operations Root Cause Tree Analysis |
|---|---|---|---|---|
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. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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 a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | 2-4 h | 1-4 h | 1-3 h |
Participantsdifferent | 1-3 | 2-8 | 3-8 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Cause Tree, Evidence Notes, Countermeasures |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OntologyKnowledge graphScopeRequirementsSemantic | Root causeProblem solvingQualityIncident | Root causeTreeIncidentQuality |



