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 for Learning Review.
Operations
Learning Review
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.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.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.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitydifferent
MediumMediumLowLow
Timedifferent
30-90 min1-3 h30-60 min30-60 min
Participantsdifferent
3-123-103-123-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineLearning Review Notes, System Factors, Improvement ActionsStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
LearningRetrospectiveIncidentOperations
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods