View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Delivery RAID Log |  Operations MORT Analysis |  Operations Fault Tree Analysis |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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 | Low | Low | High | High |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | Mehrere Tage bis Wochen | 2-6 h |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 2-6 | 3-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | RAID Log, Status Report Source | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | AlignmentStakeholdersTeam | RiskTrackingStakeholdersGovernance | Root causeSafetySystemicIncident | RiskRoot causeSafety |