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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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.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
MediumMediumLow
Timedifferent
30-90 min1-2 h Setup, laufend10-20 min daily
Participantsdifferent
3-1211
Formatdifferent
Workshop + asyncAsyncAsync
Outputdifferent
Postmortem Doc, Action Items, TimelineAction Lists, Project List, Review RoutineDaily Plan, Time Estimates, Review Notes
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
ProductivityPlanningTasksExecution
PlanningTime managementProductivityOperations
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Learning Review.
Operations
Learning Review
A paper tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
Paper illustration for Weekly Review.
Operations
Weekly Review