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) |  Product Discovery Riskiest Assumption Test |
|---|---|---|---|
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. | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | 1-4 h | 2–4 h review as a planning range; preparation and evaluation additional | 1-2 Wochen pro Iteration |
Participantsdifferent | 3-8 | Designers, developers as users, and facilitation | 2-6 |
Formatdifferent | Workshop | Workshop + async | 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 | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | RiskDecisionSensemaking | ArchitectureEngineeringFeedbackValidationTasks | ExperimentsValidationDiscoveryAssumptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
