View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Design Storyboarding |  Innovation Design Thinking |  Architecture Architecture Decision Record |  Product Discovery Outcome-Driven Innovation |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 30-90 min | 1 Tag bis mehrere Wochen | 15-45 min | Mehrere Wochen |
Participantsdifferent | 1-8 | 4-10 | 1-3 | 2-6 researchers plus sample |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Storyboard, Concept Narrative, Testable Assumptions | Problem Statement, Prototype, Test Learnings | ADR File, Decision Log, Rationale | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses |
Tagsno overlap | VisualizationConceptsSequencePrototype | InnovationPrototypeResearch | ArchitectureRationaleDocumentationGovernance | OutcomesInnovationResearchQuantitative |