View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team Topologies Interaction ModesBlameless PostmortemStart Stop ContinueSailboat Retrospective
| Criterion |  Team Design Team Topologies Interaction Modes |  DevOps Blameless Postmortem |  Agile Start Stop Continue |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | Half day | 30-90 min | 30-60 min | 45-90 min |
Participantsdifferent | Team-Leads plus Architecture | 3-12 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Postmortem Doc, Action Items, Timeline | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | TeamAlignmentCollaborationOrganization | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement |