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 | ![]() Business Strategy Scenario Planning | ![]() Knowledge Modeling Knowledge Mapping |
|---|---|---|---|
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. | Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 30-90 min | 0.5-2 Tage | 1-3 h |
Participantsdifferent | 1-8 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Storyboard, Concept Narrative, Testable Assumptions | Scenario Set, Strategic Implications, Robust Options | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | VisualizationConceptsSequencePrototype | StrategyUncertaintyPlanning | KnowledgeMappingRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






