View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Solution Interview |  Facilitation Stakeholder Salience Model |  Architecture Architecture Decision Record |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-60 min je Interview | 60-90 min | 15-45 min | 1-2 h |
Participantsdifferent | 5-10 Interviews | 3-6 | 1-3 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | Salience Diagram, Strategy per Class | ADR File, Decision Log, Rationale | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ValidationInterviewsPrototype | StakeholdersFacilitationAlignmentGovernance | ArchitectureRationaleDocumentationGovernance | AlignmentStakeholdersStrategyFacilitation |