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 |  Decision Making Pre-Mortem |  Delivery RAID Log |  Delivery Communication Plan |
|---|---|---|---|---|
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. | 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 20–45 min | 30 min Setup, dann laufend | 45-90 min |
Participantsdifferent | 3-20 Reviewer | Small cross-functional group | 1-3 maintaining, briefing for everyone | 2-6 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Risk list, Mitigation plan, Assumption log | RAID Log, Status Report Source | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskDecisionFailurePlanning | RiskTrackingStakeholdersGovernance | CommunicationStakeholdersDeliveryPlanning |