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 | ![]() UX Research Tree Testing | ![]() Architecture C4 Model | ![]() Architecture arc42 |
|---|---|---|---|---|
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. | When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-90 min | 1-2 Tage | 1-4 h | 1-2 Tage |
Participantsdifferent | 1-8 | Based on research question | 1-5 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Storyboard, Concept Narrative, Testable Assumptions | Findability Metrics, Path Analysis, Revised IA | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | VisualizationConceptsSequencePrototype | Information architectureNavigationFindability | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication |



