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 |  DevOps Blameless Postmortem |  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. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective 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 | Medium | Low | Medium |
Timedifferent | 20-40 min initial, dann laufend | 30-90 min | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 3-15 | 3-12 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | ROAM Board, Owner List | Postmortem Doc, Action Items, Timeline | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskAgileTrackingAlignment | Site Reliability EngineeringIncidentLearningReliability | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |