View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Facilitation Expectation Mapping |  Agile ROAM Board |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | 45-90 min | 20-40 min initial, dann laufend | 30 min Setup, dann laufend |
Participantsdifferent | 1-3 | 3-12 | 3-15 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Expectation Map, Alignment Notes, Agreements | ROAM Board, Owner List | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AlignmentStakeholdersTeam | RiskAgileTrackingAlignment | RiskTrackingStakeholdersGovernance |