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 |  Architecture Architecture Decision Record |  Product Discovery Outcome-Driven Innovation |  Architecture C4 Model |
|---|---|---|---|---|
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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 30-90 min | 15-45 min | Mehrere Wochen | 1-4 h |
Participantsdifferent | 1-8 | 1-3 | 2-6 researchers plus sample | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Storyboard, Concept Narrative, Testable Assumptions | ADR File, Decision Log, Rationale | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | VisualizationConceptsSequencePrototype | ArchitectureRationaleDocumentationGovernance | OutcomesInnovationResearchQuantitative | ArchitectureCommunicationVisualization |