View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile ROAM Board |  Decision Making Pre-Mortem |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 20-40 min initial, dann laufend | 20–45 min | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 3-15 | Small cross-functional group | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | ROAM Board, Owner List | Risk list, Mitigation plan, Assumption log | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskAgileTrackingAlignment | RiskDecisionFailurePlanning | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |