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 |  Systems Thinking Systems Mapping |  Decision Making Force Field Analysis |  Knowledge Modeling Concept 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. | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-90 min | 1-3 h | 45-90 min | 1-2 h |
Participantsdifferent | 1-8 | 3-12 | 3-12 | 1-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Storyboard, Concept Narrative, Testable Assumptions | System Map, Dependencies, Leverage Points | Force Field Map, Change Levers, Risk Notes | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | VisualizationConceptsSequencePrototype | Systems thinkingMappingBoundariesChange | ChangeDecisionStrategy | KnowledgeConceptsMappingSensemaking |