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 Alignment Mapping | ![]() Product Strategy Counter Metrics | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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 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 a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. | 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 | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 1-2 h | 30-60 min | 60-90 min |
Participantsdifferent | 1-3 | 4-12 | 2-6 | 3-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Alignment Map, Open Issues, Decision Questions | Counter Metric List, Guardrail Definitions | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AlignmentStakeholdersStrategyFacilitation | MetricsMeasurementStrategyExperiments | StakeholdersFacilitationAlignmentGovernance |



