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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Kaizen Event.
Operations
Kaizen Event
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
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 tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.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
HighMediumMediumLow
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope0.5-5 Tage45-120 min15-30 min
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting4-102-62-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesKaizen Charter, Waste List, Improvement Experiments, Standard Work UpdateChange Matrix, Cause Hypotheses, Validation Questions, Action ListRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
LeanContinuous improvementOperations
ChangeRoot causeTroubleshootingComparison
Root causeIncidentLeanProblem solving
Add more methods