View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Contextual Inquiry |  DevOps Blameless Postmortem |  DevOps Game Day |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | 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. | 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 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 | High | Low |
Timedifferent | 1-3 Wochen | 30-90 min | Halber Tag | 20-45 min |
Participantsdifferent | 4-12 Beobachtungen | 3-12 | 5-20 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Postmortem Doc, Action Items, Timeline | Simulation Notes, Gaps List, Updated Runbooks | Lessons learned, Action items, Event summary |
Tagsno overlap | UX researchObservationContext | Site Reliability EngineeringIncidentLearningReliability | ResilienceOperationsIncident | LearningOperationsImprovement |