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 Red Teaming |  Architecture Request for Comments |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | Low | High | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 1-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-8 | 3-20 Reviewer | 2-8 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Challenge Findings, Risk Register, Mitigation Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RiskDecisionSensemaking | ArchitectureDecisionAsyncGovernance | AssumptionsRiskDecisionDiscovery |