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 RAID Log |  Operations Gemba Walk |  UX Research Contextual Inquiry |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 30 min Setup, dann laufend | 30-120 min | 1-3 Wochen | 2-6 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-6 | 4-12 Beobachtungen | 3-10 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Observation Notes, Improvement Ideas | Field Notes, Workflow Insights, Pain Points | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | LeanObservationProcessOperations | UX researchObservationContext | RiskQualityOperationsRoot cause |