View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Learning Review |  Delivery RAID Log |  Operations Fishbone Diagram |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 30-60 min | 1-4 h |
Participantsdifferent | 3-10 | 1-3 maintaining, briefing for everyone | 2-8 | 3-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Learning Review Notes, System Factors, Improvement Actions | RAID Log, Status Report Source | Fishbone Diagram, Cause Categories, Investigation Backlog | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | LearningRetrospectiveIncidentOperations | RiskTrackingStakeholdersGovernance | Root causeQualityOperations | Root causeProblem solvingQualityIncident |