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 | ![]() Delivery RAID Log | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Low | Medium |
Timedifferent | 30–60 min per interview | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 1 participant per interview | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Interview Notes, Themes, Insight Summary | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | QualitativeResearchCustomerDiscovery | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






