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 Shape Up |  DevOps Blameless Postmortem |  DevOps Incident Command |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | 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. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 30-90 min | As needed | 20-45 min |
Participantsdifferent | 2-4 pro Pitch | 3-12 | 4-15 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Postmortem Doc, Action Items, Timeline | Incident Log, Action Tracker, Stakeholder Updates | Lessons learned, Action items, Event summary |
Tagsno overlap | PlanningDeliveryAutonomy | Site Reliability EngineeringIncidentLearningReliability | IncidentOperationsReliability | LearningOperationsImprovement |