View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Opportunity Interview |  Architecture Software Architecture Canvas |  Product Discovery Problem Interview |  Architecture Risk Storming |
|---|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-60 min je Interview | 1-2 h | 30-60 min je Interview | 60-90 min |
Participantsdifferent | 5-12 Interviews | 3-10 | 5-12 Interviews | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Architecture Canvas, Goals, Constraints, Quality Attributes | Problem Evidence, Risk Notes, Customer Segments | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | CanvasArchitectureAlignmentWorkshop | DiscoveryInterviewsValidation | RiskArchitectureWorkshopValidation |