View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Decision Making Argument Mapping | ![]() Architecture Views and Beyond | ![]() Decision Making Red Teaming |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Medium | High |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 1-3 Tage | 1-4 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-8 | 1-4 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Argument Map, Evidence Gaps, Decision Rationale | Architecture Views, Cross-view Notes, Rationale | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | SensemakingDecisionRationale | DocumentationStakeholdersArchitecture | RiskDecisionSensemaking |



