View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Change AnalysisOutcome-Driven InnovationDesign ThinkingSAAM (Software Architecture Analysis Method)
| Criterion |  Operations Change Analysis |  Product Discovery Outcome-Driven Innovation |  Innovation Design Thinking |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | 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 complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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 | High | High | High |
Timedifferent | 45-120 min | Mehrere Wochen | 1 Tag bis mehrere Wochen | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 2-6 | 2-6 researchers plus sample | 4-10 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Statement, Prototype, Test Learnings | 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 | ChangeRoot causeTroubleshootingComparison | OutcomesInnovationResearchQuantitative | InnovationPrototypeResearch | ArchitectureChangeAnalysisComparisonQuality |