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 Fishbowl Discussion.
Facilitation
Fishbowl Discussion
Paper illustration for Peer Instruction.
Knowledge Modeling
Peer Instruction
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.When a controversial topic needs depth and discipline at the same time, Fishbowl Discussion makes the structure of the conversation transparent. The format keeps the core small enough for real dialogue and open enough for controlled turnover.Peer Instruction uses group thinking to clarify difficult terms or concepts faster. The method combines individual reflection with social correction and shared precision.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
45–75 min30-90 min45-90 min10-20 min je Frage
Participantsdifferent
Team members involved3-128-806-50
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsPostmortem Doc, Action Items, TimelineDiscussion Insights, Observed Tensions, Follow-up QuestionsConcept Questions, Vote Results, Learning Notes
Tagsno overlap
RetrospectiveLearningReflectionTeam
Site Reliability EngineeringIncidentLearningReliability
FacilitationDialogueLarge group
LearningDialogueFacilitation
Add more methods