View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy Impact Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Root Cause Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. | 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. | 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 | Medium | High | Medium | Low |
Timedifferent | 45-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | 1-4 h | 15-30 min |
Participantsdifferent | 3-8 | Architecture experts and stakeholders for scenarios and weighting | 3-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Impact Map, Outcome Hypotheses, Delivery Options | 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 alternatives | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | OutcomesStrategyBehaviorPlanning | ArchitectureChangeAnalysisComparisonQuality | Root causeProblem solvingQualityIncident | Root causeIncidentLeanProblem solving |