Compare

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 Innovation Context Canvas Quality Attribute Workshop Software Architecture Canvas

Criterion	Product Discovery Outcome-Driven Innovation	Product Discovery Context Canvas	Architecture Quality Attribute Workshop	Architecture Software Architecture 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.	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.	A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties.	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.
Complexitydifferent	High	Low	Medium	Low
Timedifferent	Mehrere Wochen	45-90 min	2-4 h	1-2 h
Participantsdifferent	2-6 researchers plus sample	3-10	5-15	3-10
Formatdifferent	Workshop + async	Workshop	Workshop	Workshop
Outputdifferent	Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses	Context canvas, Open questions, Shared context notes	Quality Scenarios, Priority List, Architecture Concerns	Architecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap	OutcomesInnovationResearchQuantitative	ContextFramingRequirementsCanvas	RequirementsArchitectureWorkshop	CanvasArchitectureAlignmentWorkshop

Add more methods