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 Kaizen Event ARID (Active Reviews for Intermediate Designs)A3 Problem Solving

Criterion	Architecture Architecture Decision Record	Operations Kaizen Event	Architecture ARID (Active Reviews for Intermediate Designs)	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.	For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.	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 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	Medium	Medium
Timedifferent	15-45 min	0.5-5 Tage	2–4 h review as a planning range; preparation and evaluation additional	45-90 min
Participantsdifferent	1-3	4-10	Designers, developers as users, and facilitation	2-5
Formatdifferent	Async	Workshop	Workshop + async	Workshop + async
Outputdifferent	ADR File, Decision Log, Rationale	Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	A3 Report, Action Plan, Root Cause Analysis
Tagsno overlap	ArchitectureRationaleDocumentationGovernance	LeanContinuous improvementOperations	ArchitectureEngineeringFeedbackValidationTasks	LeanProblem solvingCoachingOperations

Add more methods