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 |  UX Design Service Blueprinting |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. |
Complexitydifferent | Low | High | Low | High |
Timedifferent | 20-40 min initial, dann laufend | 0.5-2 Tage | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-15 | 6-12 | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | ROAM Board, Owner List | Service Blueprint, Fail Points, Ownership Map | RAID Log, Status Report Source | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | RiskAgileTrackingAlignment | Service designOperationsJourneyBlueprint | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders |