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 Risk Storming |  Architecture arc42 |
|---|---|---|---|
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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | High | Low | Low |
Timedifferent | Mehrere Wochen | 60-90 min | 1-2 Tage |
Participantsdifferent | 2-6 researchers plus sample | 4-12 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Annotated Diagram, Prioritized Risk List, Action Backlog | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | OutcomesInnovationResearchQuantitative | RiskArchitectureWorkshopValidation | ArchitectureDocumentationCommunication |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
