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 Learning Review.
Operations
Learning Review
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
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
Purposedifferent
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.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.
Complexitydifferent
MediumLowLow
Timedifferent
1-3 h20-60 min45–75 min
Participantsdifferent
3-101-4Team members involved
Formatdifferent
WorkshopAsyncWorkshop
Outputdifferent
Learning Review Notes, System Factors, Improvement ActionsRunbook, Checklist, Escalation Path4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
LearningRetrospectiveIncidentOperations
OperationsReliabilityDocumentation
RetrospectiveLearningReflectionTeam
Add more methods

Often compared together

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

Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue