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 Assumption Surfacing | ![]() Decision Making Red Teaming | ![]() Architecture Risk Storming | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 45-90 min | 1-4 h | 60-90 min | 45-60 min |
Participantsdifferent | 2-8 | 3-8 | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Challenge Findings, Risk Register, Mitigation Plan | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption map, Test backlog, Risk ranking |
Tags1 shared | AssumptionsRiskDecisionDiscovery | RiskDecisionSensemaking | RiskArchitectureWorkshopValidation | AssumptionsRiskExperimentsValidation |



