View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Communication Plan |  Decision Making Pre-Mortem |  Architecture Architecture Decision Record |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 20–45 min | 15-45 min | 30 min Setup, dann laufend |
Participantsdifferent | 2-6 | Small cross-functional group | 1-3 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | Risk list, Mitigation plan, Assumption log | ADR File, Decision Log, Rationale | RAID Log, Status Report Source |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | RiskDecisionFailurePlanning | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance |