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 |  Knowledge Modeling Feynman Technique |  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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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 | 20-60 min | 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 | Plain-language Explanation, Knowledge Gaps, Study Notes | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | LearningKnowledgeUnderstanding | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement |