View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Opportunity InterviewLASR (Lightweight Approach for Software Reviews)Problem Framing WorkshopATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Product Discovery Opportunity Interview |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Problem Framing Workshop |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | 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 a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | 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 | Medium | Medium | Low | High |
Timedifferent | 30-60 min je Interview | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-120 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 5-12 Interviews | 1 or a small team; particularly suitable for 3–4 people | 4-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | 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 | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | 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 | DiscoveryInterviewsOpportunityCustomer | ArchitectureQualityRiskAssessmentLean | FacilitationAlignmentDiscovery | ArchitectureQualityRiskTradeoffsStakeholders |