View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)Outcome-Driven Innovation5 WhysRoot Cause Analysis
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Product Discovery Outcome-Driven Innovation |  Operations 5 Whys |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. | 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. |
Complexitydifferent | High | High | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | Mehrere Wochen | 15-30 min | 1-4 h |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-6 researchers plus sample | 2-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 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 | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | OutcomesInnovationResearchQuantitative | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |