View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Constraint Analysis |  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. | 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. | 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 |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-90 min | 1-3 h |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 1-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ConstraintsDecisionPlanningOptions | SensemakingDecisionRationale |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
