View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Working BackwardsATAM (Architecture Tradeoff Analysis Method)LASR (Lightweight Approach for Software Reviews)Architecture Inception Canvas
| Criterion |  Product Discovery Working Backwards |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Architecture Inception Canvas |
|---|---|---|---|---|
Purposedifferent | When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration. | 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. | 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 4-8 h, mehrere Iterationen | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-2 h |
Participantsdifferent | 2-6 | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Future Press Release, FAQ, Vision Statement | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | 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 | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | VisionNarrativeAlignment | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean | AlignmentArchitectureCanvas |