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)
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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
HighMediumLowHigh
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scopeAs needed15-30 min2-6 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders4-152-63-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsIncident Log, Action Tracker, Stakeholder UpdatesRoot cause notes, CountermeasuresFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
IncidentOperationsReliability
Root causeIncidentLeanProblem solving
RiskQualityOperationsRoot cause
Add more methods