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 |  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. | 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. | 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 | High | Low | Low |
Timedifferent | 30-90 min | 1 Tag bis mehrere Wochen | 15-45 min | 1-4 h |
Participantsdifferent | 1-8 | 4-10 | 1-3 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Storyboard, Concept Narrative, Testable Assumptions | Problem Statement, Prototype, Test Learnings | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | VisualizationConceptsSequencePrototype | InnovationPrototypeResearch | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization |