methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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.
Complexitydifferent
MediumHighMediumLow
Timedifferent
1-2 h Setup, laufendHalber TagAs needed10-20 min daily
Participantsdifferent
15-204-151
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
Action Lists, Project List, Review RoutineSimulation Notes, Gaps List, Updated RunbooksIncident Log, Action Tracker, Stakeholder UpdatesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
ProductivityPlanningTasksExecution
ResilienceOperationsIncident
IncidentOperationsReliability
PlanningTime managementProductivityOperations
Add more methods