View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Double Diamond |  DevOps Game Day |  DevOps Blameless Postmortem |  Operations Gemba Walk |
|---|---|---|---|---|
Purposedifferent | For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement. | 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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | Wochen bis Monate | Halber Tag | 30-90 min | 30-120 min |
Participantsdifferent | 3-12 | 5-20 | 3-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | Simulation Notes, Gaps List, Updated Runbooks | Postmortem Doc, Action Items, Timeline | Observation Notes, Improvement Ideas |
Tagsno overlap | ProcessDivergenceInnovation | ResilienceOperationsIncident | Site Reliability EngineeringIncidentLearningReliability | LeanObservationProcessOperations |