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 |  UX Design Storyboarding |  Architecture arc42 |  Innovation Design Thinking |
|---|---|---|---|---|
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 a usage scenario needs to become understandable early, it condenses situations, context, and flow into a legible sequence. It helps check concept ideas before anything gets built. | 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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. |
Complexitydifferent | High | Medium | Low | High |
Timedifferent | Mehrere Wochen | 30-90 min | 1-2 Tage | 1 Tag bis mehrere Wochen |
Participantsdifferent | 2-6 researchers plus sample | 1-8 | 1-4 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Storyboard, Concept Narrative, Testable Assumptions | Architecture Document, Context View, Runtime View, Deployment View | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | OutcomesInnovationResearchQuantitative | VisualizationConceptsSequencePrototype | ArchitectureDocumentationCommunication | InnovationPrototypeResearch |