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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Change Analysis.
Operations
Change Analysis
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.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.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
MediumHighMediumLow
Timedifferent
30-90 minPreparation, scenario analysis, and findings review; effort depends on scope45-120 min15-30 min
Participantsdifferent
3-12Architecture experts and stakeholders for scenarios and weighting2-62-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesChange Matrix, Cause Hypotheses, Validation Questions, Action ListRoot cause notes, Countermeasures
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
ArchitectureChangeAnalysisComparisonQuality
ChangeRoot causeTroubleshootingComparison
Root causeIncidentLeanProblem solving
Add more methods