View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Runbook |
|---|---|---|---|
Purposedifferent | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. |
Complexitydifferent | Low | High | Low |
Timedifferent | 15-45 min | Several meetings plus preparation and analysis; total effort depends on scope | 20-60 min |
Participantsdifferent | 1-3 | Evaluation team, architects, and relevant stakeholders | 1-4 |
Formatdifferent | Async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Runbook, Checklist, Escalation Path |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureQualityRiskTradeoffsStakeholders | OperationsReliabilityDocumentation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
