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 |  Architecture Risk Storming |  Architecture Architecture Communication Canvas |  Delivery RAID Log |
|---|---|---|---|---|
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 architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Low | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min | 60-120 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-20 Reviewer | 4-12 | 2-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop | Workshop + async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Annotated Diagram, Prioritized Risk List, Action Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskArchitectureWorkshopValidation | ArchitectureCommunicationStakeholdersCanvas | RiskTrackingStakeholdersGovernance |