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 Mad Sad Glad
Agile
Mad Sad Glad
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
LowLowMediumLow
Timedifferent
5-20 min30-60 min30-90 min30-60 min
Participantsdifferent
2-83-103-123-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Understanding Check, Clarification Notes, Learning GapsEmotion Board, Themes, Action ItemsPostmortem Doc, Action Items, TimelineStart Stop Continue Board, Improvement Actions
Tagsno overlap
LearningUnderstandingCommunication
RetrospectiveTeamReflection
Site Reliability EngineeringIncidentLearningReliability
RetrospectiveImprovementTeamReflection
Add more methods