View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:GAP AnalysisATAM (Architecture Tradeoff Analysis Method)5 WhysFailure Mode and Effects Analysis
| Criterion | ![]() Business Strategy GAP Analysis | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Operations 5 Whys | ![]() Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | 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 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. | 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 | High | Low | High |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 15-30 min | 2-6 h |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 2-6 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Root cause notes, Countermeasures | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | StrategyAnalysisPlanning | ArchitectureQualityRiskTradeoffsStakeholders | Root causeIncidentLeanProblem solving | RiskQualityOperationsRoot cause |



