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 |  DevOps Incident Timeline Analysis |  Agile ROAM Board |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 60-180 min | 20-40 min initial, dann laufend | 1-2 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-10 | 3-15 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions | ROAM Board, Owner List | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | IncidentTimelineSite Reliability Engineering | RiskAgileTrackingAlignment | AlignmentStakeholdersStrategyFacilitation |