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 Risk Storming |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Argument Mapping |  Decision Making Red Teaming |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 60-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 1-4 h |
Participantsdifferent | 4-12 | Designers, developers as users, and facilitation | 1-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Argument Map, Evidence Gaps, Decision Rationale | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | RiskArchitectureWorkshopValidation | ArchitectureEngineeringFeedbackValidationTasks | SensemakingDecisionRationale | RiskDecisionSensemaking |