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 Argument Mapping |  Architecture arc42 |  Decision Making Red Teaming |
|---|---|---|---|---|
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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 45-90 min | 1-3 h | 1-2 Tage | 1-4 h |
Participantsdifferent | 2-8 | 1-8 | 1-4 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Argument Map, Evidence Gaps, Decision Rationale | Architecture Document, Context View, Runtime View, Deployment View | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | SensemakingDecisionRationale | ArchitectureDocumentationCommunication | RiskDecisionSensemaking |