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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
HighHighMediumHigh
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scopeHalber Tag30-90 min2-6 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders5-203-123-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsSimulation Notes, Gaps List, Updated RunbooksPostmortem Doc, Action Items, TimelineFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
ResilienceOperationsIncident
Site Reliability EngineeringIncidentLearningReliability
RiskQualityOperationsRoot cause
Add more methods