View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Timeline |  Architecture C4 Model |  UX Design Storyboarding |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When a project, incident, or change process is only remembered in fragments, Timeline brings the sequence back into a readable form. It makes turning points, precursors, and after-effects recognizable over the course of time. | 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. | 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 30-90 min | 1-4 h | 30-90 min | 1-2 Tage |
Participantsdifferent | 2-12 | 1-5 | 1-8 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Timeline, Milestones, Insight Notes | Context Diagram, Container Diagram, Component Diagram | Storyboard, Concept Narrative, Testable Assumptions | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | TimelineFacilitationSequence | ArchitectureCommunicationVisualization | VisualizationConceptsSequencePrototype | ArchitectureDocumentationCommunication |