View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Delivery RAID Log |  Decision Making Red Teaming |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend | 1-4 h | 60-120 min |
Participantsdifferent | 3-20 Reviewer | 1-3 maintaining, briefing for everyone | 3-8 | 2-8 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source | Challenge Findings, Risk Register, Mitigation Plan | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance | RiskDecisionSensemaking | ArchitectureCommunicationStakeholdersCanvas |