View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  UX Design Storyboarding |  Operations ALPEN Method |  Operations Getting Things Done |
|---|---|---|---|---|
Purposedifferent | 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. | 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 | Low | Medium | Low | Medium |
Timedifferent | 1-4 h | 30-90 min | 10-20 min daily | 1-2 h Setup, laufend |
Participantsdifferent | 1-5 | 1-8 | 1 | 1 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Storyboard, Concept Narrative, Testable Assumptions | Daily Plan, Time Estimates, Review Notes | Action Lists, Project List, Review Routine |
Tagsno overlap | ArchitectureCommunicationVisualization | VisualizationConceptsSequencePrototype | PlanningTime managementProductivityOperations | ProductivityPlanningTasksExecution |