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

Criterion	Architecture Quality Attribute Workshop	Product Discovery Outcome-Driven Innovation	Product Discovery Context Canvas	Architecture Software Architecture Canvas
Purposedifferent	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.	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.	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	Medium	High	Low	Low
Timedifferent	2-4 h	Mehrere Wochen	45-90 min	1-2 h
Participantsdifferent	5-15	2-6 researchers plus sample	3-10	3-10
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop
Outputdifferent	Quality Scenarios, Priority List, Architecture Concerns	Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses	Context canvas, Open questions, Shared context notes	Architecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap	RequirementsArchitectureWorkshop	OutcomesInnovationResearchQuantitative	ContextFramingRequirementsCanvas	CanvasArchitectureAlignmentWorkshop

Add more methods