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 Argument Mapping |  DevOps Blameless Postmortem |  Architecture Architecture Decision Record |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 30-90 min | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-8 | 3-12 | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Argument Map, Evidence Gaps, Decision Rationale | Postmortem Doc, Action Items, Timeline | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | SensemakingDecisionRationale | Site Reliability EngineeringIncidentLearningReliability | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |