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)Argument Mapping Weekly Review Constraint Analysis

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Decision Making Argument Mapping	Operations Weekly Review	Decision Making Constraint Analysis
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.	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.	In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.	When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent	Medium	Medium	Low	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	1-3 h	30-60 min	30-90 min
Participantsdifferent	Designers, developers as users, and facilitation	1-8	1	2-8
Formatdifferent	Workshop + async	Workshop + async	Async	Workshop + async
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Argument Map, Evidence Gaps, Decision Rationale	Updated Task System, Weekly Focus, Next Actions	Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	SensemakingDecisionRationale	ProductivityExecutionPlanning	ConstraintsDecisionPlanningOptions

Add more methods