View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Product Discovery Outcome-Driven Innovation |  Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | High | Low |
Timedifferent | 60-90 min | Mehrere Wochen | 1-2 h |
Participantsdifferent | 4-12 | 2-6 researchers plus sample | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | RiskArchitectureWorkshopValidation | OutcomesInnovationResearchQuantitative | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
