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 ARID (Active Reviews for Intermediate Designs) |  Decision Making Decision Rights Mapping |  Architecture arc42 |  Decision Making DACI |
|---|---|---|---|---|
Purposedifferent | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 90-180 min | 1-2 Tage | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 4-12 | 1-4 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Decision Rights Matrix, Agreement | Architecture Document, Context View, Runtime View, Deployment View | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | DecisionGovernanceAlignmentResponsibility | ArchitectureDocumentationCommunication | DecisionRolesGovernanceAlignment |