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:Architecture Decision Record ARID (Active Reviews for Intermediate Designs)5 Whys A3 Problem Solving

Criterion	Architecture Architecture Decision Record	Architecture ARID (Active Reviews for Intermediate Designs)	Operations 5 Whys	Operations A3 Problem Solving
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.	For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.	For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.
Complexitydifferent	Low	Medium	Low	Medium
Timedifferent	15-45 min	2–4 h review as a planning range; preparation and evaluation additional	15-30 min	45-90 min
Participantsdifferent	1-3	Designers, developers as users, and facilitation	2-6	2-5
Formatdifferent	Async	Workshop + async	Workshop	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	Root cause notes, Countermeasures	A3 Report, Action Plan, Root Cause Analysis
Tagsno overlap	ArchitectureRationaleDocumentationGovernance	ArchitectureEngineeringFeedbackValidationTasks	Root causeIncidentLeanProblem solving	LeanProblem solvingCoachingOperations

Add more methods