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
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.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
LowHighLow
Timedifferent
20-45 minHalber Tag45–75 min
Participantsdifferent
1-85-20Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Ownership Reflection, Action Commitment, Coaching NotesSimulation Notes, Gaps List, Updated Runbooks4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ResponsibilityLeadershipTeam
ResilienceOperationsIncident
RetrospectiveLearningReflectionTeam
Add more methods

Often compared together

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

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 of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review