View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  DevOps Blameless Postmortem |  Agile Sailboat Retrospective |  Operations Learning Review |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | 30-90 min | 45-90 min | 1-3 h |
Participantsdifferent | 3-12 | 3-12 | 4-12 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Postmortem Doc, Action Items, Timeline | Sailboat Board, Risks, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | AlignmentStakeholdersTeam | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveTeamImprovement | LearningRetrospectiveIncidentOperations |