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 |  Knowledge Modeling Knowledge Mapping |  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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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 | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 20–45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-12 | Small cross-functional group |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Risk list, Mitigation plan, Assumption log |
Tags1 shared | RiskTrackingStakeholdersGovernance | KnowledgeMappingRisk | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
