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 Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Purposedifferent
For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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.
Complexitysame
MediumMediumMedium
Timedifferent
60-180 minOngoing1-2 h Setup, laufend
Participantsdifferent
3-102-201
Formatdifferent
Workshop + asyncWorkshop + asyncAsync
Outputdifferent
Incident Timeline, Evidence Log, Delay Analysis, Improvement ActionsChat Transcript, Action Log, AutomationsAction Lists, Project List, Review Routine
Tagsno overlap
IncidentTimelineSite Reliability Engineering
CollaborationEngineeringIncident
ProductivityPlanningTasksExecution
Add more methods

Often compared together

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

Paper illustration for Weekly Review.
Operations
Weekly Review
Paper illustration for ALPEN Method
Operations
ALPEN Method
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem