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 arc42 |  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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | 1-2 Tage | 45-60 min |
Participantsdifferent | 2-8 | 3-8 | 1-4 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Challenge Findings, Risk Register, Mitigation Plan | Architecture Document, Context View, Runtime View, Deployment View | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | RiskDecisionSensemaking | ArchitectureDocumentationCommunication | AssumptionsRiskExperimentsValidation |