View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Communication Plan | ![]() Agile Sailboat Retrospective | ![]() Agile Start Stop Continue |
|---|---|---|---|
Purposedifferent | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitysame | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 30-60 min |
Participantsdifferent | 2-6 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






