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:ARID (Active Reviews for Intermediate Designs)Architecture Decision Record OODA Loop Argument Mapping

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Architecture Architecture Decision Record	Decision Making OODA Loop	Decision Making Argument Mapping
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.	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.	In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.	When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitydifferent	Medium	Low	Medium	Medium
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	15-45 min	15-60 min je Zyklus	1-3 h
Participantsdifferent	Designers, developers as users, and facilitation	1-3	1-8	1-8
Formatdifferent	Workshop + async	Async	Workshop + async	Workshop + async
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	ADR File, Decision Log, Rationale	Situation Assessment, Decision Loop, Action Updates	Argument Map, Evidence Gaps, Decision Rationale
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	ArchitectureRationaleDocumentationGovernance	DecisionChangeLearningStrategy	SensemakingDecisionRationale

Add more methods