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 Risk Storming |  Product Discovery Fake Door Test |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | 1-4 h | 60-90 min | 1-5 Tage | 45-90 min |
Participantsdifferent | 3-8 | 4-12 | Nutzertraffic | 2-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Challenge Findings, Risk Register, Mitigation Plan | Annotated Diagram, Prioritized Risk List, Action Backlog | Click Data, Interest Signal, Learning Decision | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskDecisionSensemaking | RiskArchitectureWorkshopValidation | ValidationExperimentsDemandDiscovery | AssumptionsRiskDecisionDiscovery |