View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Jobs to Be Done |  Delivery RAID Log |  Operations Fishbone Diagram |  Operations Fault Tree Analysis |
|---|---|---|---|---|
Purposedifferent | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 1-3 Wochen | 30 min Setup, dann laufend | 30-60 min | 2-6 h |
Participantsdifferent | 5-12 Interviews | 1-3 maintaining, briefing for everyone | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | RAID Log, Status Report Source | Fishbone Diagram, Cause Categories, Investigation Backlog | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | CustomerOutcomesNeeds | RiskTrackingStakeholdersGovernance | Root causeQualityOperations | RiskRoot causeSafety |