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 ALPEN Method |  Operations MORT Analysis |  Operations Family Tree 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. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. | 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 series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 30 min Setup, dann laufend | 10-20 min daily | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1 | 2-6 | 2-6 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Daily Plan, Time Estimates, Review Notes | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | RiskTrackingStakeholdersGovernance | PlanningTime managementProductivityOperations | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |