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 Discovery Outcome-Driven Innovation |  Architecture SAAM (Software Architecture Analysis Method) |  Operations 5 Whys |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | High | High | Low |
Timedifferent | Mehrere Wochen | Preparation, scenario analysis, and findings review; effort depends on scope | 15-30 min |
Participantsdifferent | 2-6 researchers plus sample | Architecture experts and stakeholders for scenarios and weighting | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | 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 | Root cause notes, Countermeasures |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureChangeAnalysisComparisonQuality | Root causeIncidentLeanProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
