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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
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.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
LowMediumMedium
Timedifferent
30-60 min30-90 min1-3 h
Participantsdifferent
3-123-123-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsPostmortem Doc, Action Items, TimelineLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
RetrospectiveImprovementTeamReflection
Site Reliability EngineeringIncidentLearningReliability
LearningRetrospectiveIncidentOperations
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 of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command