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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.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 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.
Complexitydifferent
MediumMediumHighLow
Timedifferent
30-90 min1-4 hSeveral meetings plus preparation and analysis; total effort depends on scope15-30 min
Participantsdifferent
3-123-8Evaluation team, architects, and relevant stakeholders2-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRoot cause notes, Countermeasures
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
Root causeProblem solvingQualityIncident
ArchitectureQualityRiskTradeoffsStakeholders
Root causeIncidentLeanProblem solving
Add more methods