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 Decision Record |  Facilitation Stakeholder Salience Model |  Engineering Goal Question Metric |
|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-45 min | 60-90 min | 90-180 min |
Participantsdifferent | 1-3 | 3-6 | 3-6 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class | GQM Table, Metric Profiles |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance | MetricsMeasurementEngineeringAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
