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 | ![]() Architecture Architecture Decision Record | ![]() Decision Making Pre-Mortem | ![]() Decision Making Argument Mapping |
|---|---|---|---|---|
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. | 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. | 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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | 90-180 min | 15-45 min | 20–45 min | 1-3 h |
Participantsdifferent | 3-8 | 1-3 | Small cross-functional group | 1-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | CoD Table, Prioritization Sequence | ADR File, Decision Log, Rationale | Risk list, Mitigation plan, Assumption log | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | ArchitectureRationaleDocumentationGovernance | RiskDecisionFailurePlanning | SensemakingDecisionRationale |



