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 illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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
MediumLowMedium
Timedifferent
30-90 min30-60 min1-2 h Setup, laufend
Participantsdifferent
3-123-121
Formatdifferent
Workshop + asyncWorkshopAsync
Outputdifferent
Postmortem Doc, Action Items, TimelineStart Stop Continue Board, Improvement ActionsAction Lists, Project List, Review Routine
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
RetrospectiveImprovementTeamReflection
ProductivityPlanningTasksExecution
Add more methods

Often compared together

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

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective