View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Pre-Mortem |  Architecture arc42 |  Facilitation Stakeholder Mapping |  Delivery Communication Plan |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20–45 min | 1-2 Tage | 60–90 min | 45-90 min |
Participantsdifferent | Small cross-functional group | 1-4 | 2-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Architecture Document, Context View, Runtime View, Deployment View | Stakeholder Map, Engagement Plan, Risk Notes | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | RiskDecisionFailurePlanning | ArchitectureDocumentationCommunication | StakeholdersAlignmentFacilitationChange | CommunicationStakeholdersDeliveryPlanning |