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 RecordARID (Active Reviews for Intermediate Designs)Competency Questions
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Knowledge Modeling Competency Questions |
|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-45 min | 2–4 h review as a planning range; preparation and evaluation additional | 2-4 h |
Participantsdifferent | 1-3 | Designers, developers as users, and facilitation | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureEngineeringFeedbackValidationTasks | OntologyKnowledge graphScopeRequirementsSemantic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






