View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Concept Mapping | ![]() Architecture arc42 | ![]() UX Design Storyboarding |
|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 1-2 h | 1-2 Tage | 30-90 min |
Participantsdifferent | 1-8 | 1-4 | 1-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Architecture Document, Context View, Runtime View, Deployment View | Storyboard, Concept Narrative, Testable Assumptions |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | ArchitectureDocumentationCommunication | VisualizationConceptsSequencePrototype |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






