methodatlas
Compare

View methods side by side.

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

Criterion
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.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
LowLowLowHigh
Timedifferent
15-45 min30-60 min20-45 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-32-83-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleFishbone Diagram, Cause Categories, Investigation BacklogLessons learned, Action items, Event summaryPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
Root causeQualityOperations
LearningOperationsImprovement
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods