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

Criterion	Operations A3 Problem Solving	Architecture ARID (Active Reviews for Intermediate Designs)	Architecture arc42	Architecture Architecture Decision Record
Purposedifferent	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.	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.	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.	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	Medium	Medium	Low	Low
Timedifferent	45-90 min	2–4 h review as a planning range; preparation and evaluation additional	1-2 Tage	15-45 min
Participantsdifferent	2-5	Designers, developers as users, and facilitation	1-4	1-3
Formatdifferent	Workshop + async	Workshop + async	Workshop + async	Async
Outputdifferent	A3 Report, Action Plan, Root Cause Analysis	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Architecture Document, Context View, Runtime View, Deployment View	ADR File, Decision Log, Rationale
Tagsno overlap	LeanProblem solvingCoachingOperations	ArchitectureEngineeringFeedbackValidationTasks	ArchitectureDocumentationCommunication	ArchitectureRationaleDocumentationGovernance

Add more methods