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 |  Decision Making Decision Rights Mapping |  Architecture Software Architecture Canvas |  Architecture Request for Comments |
|---|---|---|---|---|
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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 20–45 min | 90-180 min | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | Small cross-functional group | 4-12 | 3-10 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop | Workshop | Async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Decision Rights Matrix, Agreement | Architecture Canvas, Goals, Constraints, Quality Attributes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | RiskDecisionFailurePlanning | DecisionGovernanceAlignmentResponsibility | CanvasArchitectureAlignmentWorkshop | ArchitectureDecisionAsyncGovernance |