View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Red Teaming |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Risk Storming |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | 1-4 h | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min | 45-60 min |
Participantsdifferent | 3-8 | Designers, developers as users, and facilitation | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Challenge Findings, Risk Register, Mitigation Plan | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskDecisionSensemaking | ArchitectureEngineeringFeedbackValidationTasks | RiskArchitectureWorkshopValidation | AssumptionsRiskExperimentsValidation |