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 |  Engineering Goal Question Metric |  Facilitation Stakeholder Salience Model |  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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 60-90 min | 1-2 h |
Participantsdifferent | 3-20 Reviewer | 3-6 | 3-6 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | GQM Table, Metric Profiles | Salience Diagram, Strategy per Class | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | MetricsMeasurementEngineeringAlignment | StakeholdersFacilitationAlignmentGovernance | AlignmentStakeholdersStrategyFacilitation |