View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Outcome-Driven InnovationSAAM (Software Architecture Analysis Method)Design ThinkingDesign Sprint
| Criterion |  Product Discovery Outcome-Driven Innovation |  Architecture SAAM (Software Architecture Analysis Method) |  Innovation Design Thinking |  Innovation Design Sprint |
|---|---|---|---|---|
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 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. | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. |
Complexitysame | High | High | High | High |
Timedifferent | Mehrere Wochen | Preparation, scenario analysis, and findings review; effort depends on scope | 1 Tag bis mehrere Wochen | 4-5 Tage |
Participantsdifferent | 2-6 researchers plus sample | Architecture experts and stakeholders for scenarios and weighting | 4-10 | 5-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | 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 | Problem Statement, Prototype, Test Learnings | Prototype, Test Findings, Decision Rationale |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureChangeAnalysisComparisonQuality | InnovationPrototypeResearch | Design sprintPrototypeValidationInnovation |