View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Value Stream Mapping5 WhysATAM (Architecture Tradeoff Analysis Method)Failure Mode and Effects Analysis
| Criterion |  Delivery Value Stream Mapping |  Operations 5 Whys |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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. | 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 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. |
Complexitydifferent | Medium | Low | High | High |
Timedifferent | 1-3 h | 15-30 min | Several meetings plus preparation and analysis; total effort depends on scope | 2-6 h |
Participantsdifferent | 4-10 | 2-6 | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Root cause notes, Countermeasures | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | LeanFlowWasteDelivery | Root causeIncidentLeanProblem solving | ArchitectureQualityRiskTradeoffsStakeholders | RiskQualityOperationsRoot cause |