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 Cost of Delay |  Decision Making Pre-Mortem |  Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | 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 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 | High | Low | Medium |
Timedifferent | 90-180 min | 20–45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-8 | Small cross-functional group | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop | Async |
Outputdifferent | CoD Table, Prioritization Sequence | Risk list, Mitigation plan, Assumption log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tags1 shared | PrioritizationDeliveryEconomicsDecision | RiskDecisionFailurePlanning | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
