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)
Paper illustration for Kaizen Event.
Operations
Kaizen Event
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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.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 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.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
HighMediumHighLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope0.5-5 Tage2-6 h15-30 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders4-103-102-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsKaizen Charter, Waste List, Improvement Experiments, Standard Work UpdateFMEA Table, Risk Priority, Mitigation ActionsRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
LeanContinuous improvementOperations
RiskQualityOperationsRoot cause
Root causeIncidentLeanProblem solving
Add more methods