View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps ChatOps |  Knowledge Modeling Teach-back |  Agile Sailboat Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together. | 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 wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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 | Medium | Low | Low | Low |
Timedifferent | Ongoing | 5-20 min | 45-90 min | 45–75 min |
Participantsdifferent | 2-20 | 2-8 | 4-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Chat Transcript, Action Log, Automations | Understanding Check, Clarification Notes, Learning Gaps | Sailboat Board, Risks, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | CollaborationEngineeringIncident | LearningUnderstandingCommunication | RetrospectiveTeamImprovement | RetrospectiveLearningReflectionTeam |