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

Criterion	Delivery Cost of Delay	Architecture ARID (Active Reviews for Intermediate Designs)	Decision Making Argument Mapping	Architecture Architecture Decision Record
Purposedifferent	Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.	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.	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.	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	High	Medium	Medium	Low
Timedifferent	90-180 min	2–4 h review as a planning range; preparation and evaluation additional	1-3 h	15-45 min
Participantsdifferent	3-8	Designers, developers as users, and facilitation	1-8	1-3
Formatdifferent	Workshop	Workshop + async	Workshop + async	Async
Outputdifferent	CoD Table, Prioritization Sequence	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Argument Map, Evidence Gaps, Decision Rationale	ADR File, Decision Log, Rationale
Tagsno overlap	PrioritizationDeliveryEconomicsDecision	ArchitectureEngineeringFeedbackValidationTasks	SensemakingDecisionRationale	ArchitectureRationaleDocumentationGovernance

Add more methods