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 Incident Timeline Analysis |  DevOps Blameless Postmortem |  Operations Learning 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. | For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 60-180 min | 30-90 min | 1-3 h |
Participantsdifferent | 2-4 pro Pitch | 3-10 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions | Postmortem Doc, Action Items, Timeline | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | PlanningDeliveryAutonomy | IncidentTimelineSite Reliability Engineering | Site Reliability EngineeringIncidentLearningReliability | LearningRetrospectiveIncidentOperations |