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 Kepner-Tregoe | ![]() Decision Making Pre-Mortem |
|---|---|---|---|---|
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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 30 min Setup, dann laufend | 10-20 min daily | 2-8 h | 20–45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1 | 2-8 | Small cross-functional group |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Daily Plan, Time Estimates, Review Notes | Problem Analysis, Decision Analysis, Risk Plan | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | RiskTrackingStakeholdersGovernance | PlanningTime managementProductivityOperations | Problem solvingRoot causeDecisionOperations | RiskDecisionFailurePlanning |



