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 Teach-back.
Knowledge Modeling
Teach-back
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
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
Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations.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 an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.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
5-20 min1-3 h2-6 h45–75 min
Participantsdifferent
2-83-103-10Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Understanding Check, Clarification Notes, Learning GapsLearning Review Notes, System Factors, Improvement ActionsEvent Timeline, Causal Factor Chart, Cause List, Corrective Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
LearningUnderstandingCommunication
LearningRetrospectiveIncidentOperations
CausalityIncidentRoot causeTimeline
RetrospectiveLearningReflectionTeam
Add more methods