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 |  Operations Change Analysis |  Operations Fishbone Diagram |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
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. | 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 45-90 min | 45-120 min | 30-60 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-8 | 2-6 | 2-8 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Impact Map, Outcome Hypotheses, Delivery Options | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Fishbone Diagram, Cause Categories, Investigation Backlog | 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 |
Tagsno overlap | OutcomesStrategyBehaviorPlanning | ChangeRoot causeTroubleshootingComparison | Root causeQualityOperations | ArchitectureChangeAnalysisComparisonQuality |