View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Delivery RAID Log |  Decision Making Pre-Mortem |  Decision Making Constraint Analysis |
|---|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. | 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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Ongoing | 30 min Setup, dann laufend | 20–45 min | 30-90 min |
Participantsdifferent | 2-12 | 1-3 maintaining, briefing for everyone | Small cross-functional group | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | RAID Log, Status Report Source | Risk list, Mitigation plan, Assumption log | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | FlowVisual managementDelivery | RiskTrackingStakeholdersGovernance | RiskDecisionFailurePlanning | ConstraintsDecisionPlanningOptions |