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 | ![]() Operations ALPEN Method | ![]() Operations Getting Things Done |
|---|---|---|---|---|
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. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 30-90 min | 0.5-2 Tage | 10-20 min daily | 1-2 h Setup, laufend |
Participantsdifferent | 1-8 | 4-12 | 1 | 1 |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Storyboard, Concept Narrative, Testable Assumptions | Scenario Set, Strategic Implications, Robust Options | Daily Plan, Time Estimates, Review Notes | Action Lists, Project List, Review Routine |
Tagsno overlap | VisualizationConceptsSequencePrototype | StrategyUncertaintyPlanning | PlanningTime managementProductivityOperations | ProductivityPlanningTasksExecution |



