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 |  Delivery RAID Log |  DevOps Blameless Postmortem |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | 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. | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 20-40 min initial, dann laufend | 30 min Setup, dann laufend | 30-90 min | 1-2 h |
Participantsdifferent | 3-15 | 1-3 maintaining, briefing for everyone | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | ROAM Board, Owner List | RAID Log, Status Report Source | Postmortem Doc, Action Items, Timeline | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | RiskAgileTrackingAlignment | RiskTrackingStakeholdersGovernance | Site Reliability EngineeringIncidentLearningReliability | AlignmentStakeholdersStrategyFacilitation |