View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations ABC Analysis | ![]() Knowledge Modeling Concept Mapping | ![]() Architecture C4 Model | ![]() UX Design Storyboarding |
|---|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 30-60 min | 1-2 h | 1-4 h | 30-90 min |
Participantsdifferent | 1-5 | 1-8 | 1-5 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | Concept Map, Relationship Labels, Knowledge Gaps | Context Diagram, Container Diagram, Component Diagram | Storyboard, Concept Narrative, Testable Assumptions |
Tagsno overlap | PrioritizationOperationsPortfolio | KnowledgeConceptsMappingSensemaking | ArchitectureCommunicationVisualization | VisualizationConceptsSequencePrototype |



