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 PARA Method | ![]() UX Design Storyboarding | ![]() Business Strategy Scenario Planning | ![]() Business Strategy GAP Analysis |
|---|---|---|---|---|
Purposedifferent | The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work. | 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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h Setup, laufend | 30-90 min | 0.5-2 Tage | 1-3 h |
Participantsdifferent | 1 | 1-8 | 4-12 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Storyboard, Concept Narrative, Testable Assumptions | Scenario Set, Strategic Implications, Robust Options | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | KnowledgeProductivityOrganization | VisualizationConceptsSequencePrototype | StrategyUncertaintyPlanning | StrategyAnalysisPlanning |



