View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research User Interviews |  Architecture Architecture Decision Record |  Facilitation Stakeholder Salience Model |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30–60 min per interview | 15-45 min | 60-90 min | 60–90 min |
Participantsdifferent | 1 participant per interview | 1-3 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | QualitativeResearchCustomerDiscovery | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance | StakeholdersAlignmentFacilitationChange |