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 |  Architecture Request for Comments |  Delivery RAID Log |
|---|---|---|---|
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. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 60-120 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend |
Participantsdifferent | 2-8 | 3-20 Reviewer | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Async | Async |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
