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 Accountability Ladder
Operations
Accountability Ladder
Paper illustration for Learning Review.
Operations
Learning Review
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
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
With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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
LowMediumHighLow
Timedifferent
20-45 min1-3 hHalber Tag45–75 min
Participantsdifferent
1-83-105-20Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Ownership Reflection, Action Commitment, Coaching NotesLearning Review Notes, System Factors, Improvement ActionsSimulation Notes, Gaps List, Updated Runbooks4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ResponsibilityLeadershipTeam
LearningRetrospectiveIncidentOperations
ResilienceOperationsIncident
RetrospectiveLearningReflectionTeam
Add more methods