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
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 Root Cause Analysis.
Operations
Root Cause Analysis
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
Purposedifferent
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.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.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.
Complexitydifferent
LowMediumHighMedium
Timedifferent
15-30 min1-4 hPreparation, scenario analysis, and findings review; effort depends on scope45-120 min
Participantsdifferent
2-63-8Architecture experts and stakeholders for scenarios and weighting2-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanDomain 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 List
Tagsno overlap
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
ArchitectureChangeAnalysisComparisonQuality
ChangeRoot causeTroubleshootingComparison
Add more methods