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 |  Product Strategy KPI Tree |
|---|---|---|---|
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. | When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min | 90-180 min initial, dann laufend |
Participantsdifferent | 3-20 Reviewer | 3-6 | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Salience Diagram, Strategy per Class | KPI Tree, Owner List |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | StakeholdersFacilitationAlignmentGovernance | MetricsStrategyAlignmentMeasurement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
