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
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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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.CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.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
LowMediumMediumMedium
Timedifferent
45–75 min30-90 min45-90 min1-3 h
Participantsdifferent
Team members involved3-123-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsPostmortem Doc, Action Items, TimelineCATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
RetrospectiveLearningReflectionTeam
Site Reliability EngineeringIncidentLearningReliability
Systems thinkingFramingStakeholders
LearningRetrospectiveIncidentOperations
Add more methods