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 Communication Canvas |  Agile ROAM Board |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | 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 | Medium | Low | Low | Medium |
Timedifferent | 60-120 min | 20-40 min initial, dann laufend | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 2-8 | 3-15 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | ROAM Board, Owner List | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | RiskAgileTrackingAlignment | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |