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 Tree Testing | ![]() Delivery RAID Log | ![]() UX Research Card Sorting | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination. | 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 content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. | 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 | Medium | Low | Low | Medium |
Timedifferent | 1-2 Tage | 30 min Setup, dann laufend | 20-45 min | 60-90 min |
Participantsdifferent | Based on research question | 1-3 maintaining, briefing for everyone | Based on research question | 3-6 |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | Findability Metrics, Path Analysis, Revised IA | RAID Log, Status Report Source | Content groups, Label set, IA hypotheses | Salience Diagram, Strategy per Class |
Tagsno overlap | Information architectureNavigationFindability | RiskTrackingStakeholdersGovernance | Information architectureNavigationStructure | StakeholdersFacilitationAlignmentGovernance |



