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 Views and Beyond | ![]() Delivery RAID Log |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-90 min | 15-45 min | 1-3 Tage | 30 min Setup, dann laufend |
Participantsdifferent | 1-8 | 1-3 | 1-4 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Storyboard, Concept Narrative, Testable Assumptions | ADR File, Decision Log, Rationale | Architecture Views, Cross-view Notes, Rationale | RAID Log, Status Report Source |
Tagsno overlap | VisualizationConceptsSequencePrototype | ArchitectureRationaleDocumentationGovernance | DocumentationStakeholdersArchitecture | RiskTrackingStakeholdersGovernance |



