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 Delegation Poker |  DevOps Game Day |  DevOps Blameless Postmortem |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | 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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 45-90 min | Halber Tag | 30-90 min | 45–75 min |
Participantsdifferent | 3-10 | 5-20 | 3-12 | Team members involved |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Simulation Notes, Gaps List, Updated Runbooks | Postmortem Doc, Action Items, Timeline | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | AutonomyRolesTeam | ResilienceOperationsIncident | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveLearningReflectionTeam |