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 |
|---|---|---|---|
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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30-90 min | 1-4 h | 30-90 min |
Participantsdifferent | 2-12 | 1-5 | 1-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Timeline, Milestones, Insight Notes | Context Diagram, Container Diagram, Component Diagram | Storyboard, Concept Narrative, Testable Assumptions |
Tagsno overlap | TimelineFacilitationSequence | ArchitectureCommunicationVisualization | VisualizationConceptsSequencePrototype |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






