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 |  Facilitation Stakeholder Salience Model |  Delivery RAID Log |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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 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. | 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 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min | 30 min Setup, dann laufend | 1-2 h |
Participantsdifferent | 3-20 Reviewer | 3-6 | 1-3 maintaining, briefing for everyone | 4-12 |
Formatdifferent | Async | Workshop | Async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Salience Diagram, Strategy per Class | RAID Log, Status Report Source | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersStrategyFacilitation |