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 Architecture Communication Canvas |  Decision Making Pre-Mortem |  Delivery RAID Log |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-120 min | 20–45 min | 30 min Setup, dann laufend | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-8 | Small cross-functional group | 1-3 maintaining, briefing for everyone | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Risk list, Mitigation plan, Assumption log | RAID Log, Status Report Source | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | RiskDecisionFailurePlanning | RiskTrackingStakeholdersGovernance | ArchitectureDecisionAsyncGovernance |