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 | ![]() Delivery RAID Log | ![]() Operations ALPEN Method | ![]() Operations Getting Things Done |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Low | Low | Medium |
Timedifferent | 1-3 h Setup, laufend | 30 min Setup, dann laufend | 10-20 min daily | 1-2 h Setup, laufend |
Participantsdifferent | 1 | 1-3 maintaining, briefing for everyone | 1 | 1 |
Formatsame | Async | Async | Async | Async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | RAID Log, Status Report Source | Daily Plan, Time Estimates, Review Notes | Action Lists, Project List, Review Routine |
Tagsno overlap | KnowledgeProductivityOrganization | RiskTrackingStakeholdersGovernance | PlanningTime managementProductivityOperations | ProductivityPlanningTasksExecution |



