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 |  Operations After-Action Review |  DevOps Blameless Postmortem |  Delivery Communication Plan |
|---|---|---|---|---|
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 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. | 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 many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 20-45 min | 30-90 min | 45-90 min |
Participantsdifferent | 2-4 pro Pitch | 3-12 | 3-12 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Lessons learned, Action items, Event summary | Postmortem Doc, Action Items, Timeline | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | PlanningDeliveryAutonomy | LearningOperationsImprovement | Site Reliability EngineeringIncidentLearningReliability | CommunicationStakeholdersDeliveryPlanning |