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 InnovationAlignment MappingLASR (Lightweight Approach for Software Reviews)Stakeholder Salience Model
| Criterion |  Product Discovery Outcome-Driven Innovation |  Facilitation Alignment Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | Mehrere Wochen | 1-2 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min |
Participantsdifferent | 2-6 researchers plus sample | 4-12 | 1 or a small team; particularly suitable for 3–4 people | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Alignment Map, Open Issues, Decision Questions | 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 | Salience Diagram, Strategy per Class |
Tagsno overlap | OutcomesInnovationResearchQuantitative | AlignmentStakeholdersStrategyFacilitation | ArchitectureQualityRiskAssessmentLean | StakeholdersFacilitationAlignmentGovernance |