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 Software Architecture Canvas |  Architecture Request for Comments |  Decision Making DACI |
|---|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 20–45 min | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min |
Participantsdifferent | Small cross-functional group | 3-10 | 3-20 Reviewer | 2-10 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Architecture Canvas, Goals, Constraints, Quality Attributes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | RiskDecisionFailurePlanning | CanvasArchitectureAlignmentWorkshop | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernanceAlignment |