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 illustration for Weekly Review.
Operations
Weekly Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.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 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
LowMediumLow
Timedifferent
30-60 min30-90 min10-20 min daily
Participantsdifferent
13-121
Formatdifferent
AsyncWorkshop + asyncAsync
Outputdifferent
Updated Task System, Weekly Focus, Next ActionsPostmortem Doc, Action Items, TimelineDaily Plan, Time Estimates, Review Notes
Tagsno overlap
ProductivityExecutionPlanning
Site Reliability EngineeringIncidentLearningReliability
PlanningTime managementProductivityOperations
Add more methods

Often compared together

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

Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
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