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 Request for Comments |  Agile ROAM Board |  Facilitation Alignment Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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 | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 20-40 min initial, dann laufend | 1-2 h | 60-90 min |
Participantsdifferent | 3-20 Reviewer | 3-15 | 4-12 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ROAM Board, Owner List | Alignment Map, Open Issues, Decision Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskAgileTrackingAlignment | AlignmentStakeholdersStrategyFacilitation | StakeholdersFacilitationAlignmentGovernance |