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 Blameless Postmortem |  Operations Time Blocking |  Agile Start Stop Continue |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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 | Low | Low | Low |
Timedifferent | 30-90 min | 15-30 min Planung, laufend | 30-60 min | 45-90 min |
Participantsdifferent | 3-12 | 1 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Blocked Calendar, Capacity View, Focus Plan | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | PlanningTime managementFocus | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement |