Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Runbook Fishbone Diagram Architecture Decision Record ATAM (Architecture Tradeoff Analysis Method)

Criterion	Operations Runbook	Operations Fishbone Diagram	Architecture Architecture Decision Record	Architecture ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent	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.	When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.	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.
Complexitydifferent	Low	Low	Low	High
Timedifferent	20-60 min	30-60 min	15-45 min	Several meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent	1-4	2-8	1-3	Evaluation team, architects, and relevant stakeholders
Formatdifferent	Async	Workshop	Async	Workshop + async
Outputdifferent	Runbook, Checklist, Escalation Path	Fishbone Diagram, Cause Categories, Investigation Backlog	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
Tagsno overlap	OperationsReliabilityDocumentation	Root causeQualityOperations	ArchitectureRationaleDocumentationGovernance	ArchitectureQualityRiskTradeoffsStakeholders

Add more methods