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 |  Architecture Request for Comments |  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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | Medium | Low |
Timedifferent | 30-90 min | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h |
Participantsdifferent | 1-8 | 1-3 | 3-20 Reviewer | 1-5 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Storyboard, Concept Narrative, Testable Assumptions | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | VisualizationConceptsSequencePrototype | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationVisualization |