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)Red TeamingLASR (Lightweight Approach for Software Reviews)Argument Mapping
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Red Teaming |  Architecture LASR (Lightweight Approach for Software Reviews) |  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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | 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 | High | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-3 h |
Participantsdifferent | Designers, developers as users, and facilitation | 3-8 | 1 or a small team; particularly suitable for 3–4 people | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Challenge Findings, Risk Register, Mitigation Plan | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RiskDecisionSensemaking | ArchitectureQualityRiskAssessmentLean | SensemakingDecisionRationale |