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 InnovationLASR (Lightweight Approach for Software Reviews)Assumption MappingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Product Discovery Outcome-Driven Innovation |  Architecture LASR (Lightweight Approach for Software Reviews) |  Product Discovery Assumption Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. |
Complexitydifferent | High | Medium | Medium | High |
Timedifferent | Mehrere Wochen | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-60 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-6 researchers plus sample | 1 or a small team; particularly suitable for 3–4 people | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Assumption map, Test backlog, Risk ranking | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureQualityRiskAssessmentLean | AssumptionsRiskExperimentsValidation | ArchitectureQualityRiskTradeoffsStakeholders |