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 Outcome-Driven Innovation |  Architecture Software Architecture Canvas |  Product Discovery Context Canvas |
|---|---|---|---|
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. | 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 an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. |
Complexitydifferent | High | Low | Low |
Timedifferent | Mehrere Wochen | 1-2 h | 45-90 min |
Participantsdifferent | 2-6 researchers plus sample | 3-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Architecture Canvas, Goals, Constraints, Quality Attributes | Context canvas, Open questions, Shared context notes |
Tagsno overlap | OutcomesInnovationResearchQuantitative | CanvasArchitectureAlignmentWorkshop | ContextFramingRequirementsCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
