Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:ABC Analysis ARID (Active Reviews for Intermediate Designs)RACI Matrix Architecture Decision Record

Criterion	Operations ABC Analysis	Architecture ARID (Active Reviews for Intermediate Designs)	Operations RACI Matrix	Architecture Architecture Decision Record
Purposedifferent	With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.	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.	With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible.	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.
Complexitydifferent	Low	Medium	Low	Low
Timedifferent	30-60 min	2–4 h review as a planning range; preparation and evaluation additional	45-90 min	15-45 min
Participantsdifferent	1-5	Designers, developers as users, and facilitation	2-8	1-3
Formatdifferent	Async	Workshop + async	Workshop + async	Async
Outputdifferent	ABC Classification, Focus Rules, Control List	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	RACI Matrix, Responsibility Map, Decision Notes	ADR File, Decision Log, Rationale
Tagsno overlap	PrioritizationOperationsPortfolio	ArchitectureEngineeringFeedbackValidationTasks	RolesResponsibilityGovernanceOperations	ArchitectureRationaleDocumentationGovernance

Add more methods