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 Starfish 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Ongoing | 5-20 min | 45-90 min | 45-90 min |
Participantsdifferent | 2-20 | 2-8 | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Chat Transcript, Action Log, Automations | Understanding Check, Clarification Notes, Learning Gaps | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | CollaborationEngineeringIncident | LearningUnderstandingCommunication | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |