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 Problem Interview | ![]() Architecture Architecture Decision Record | ![]() Facilitation Stakeholder Salience Model | ![]() Facilitation Power Interest Grid |
|---|---|---|---|---|
Purposedifferent | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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. | When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-60 min je Interview | 15-45 min | 60-90 min | 30-60 min |
Participantsdifferent | 5-12 Interviews | 1-3 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class | Power Interest Grid, Strategy per Stakeholder |
Tagsno overlap | DiscoveryInterviewsValidation | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance | StakeholdersFacilitationAlignmentPlanning |



