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 Card Sorting |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 20-45 min | 30 min Setup, dann laufend | 60-90 min | 20-40 min initial, dann laufend |
Participantsdifferent | Based on research question | 1-3 maintaining, briefing for everyone | 3-6 | 3-15 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Content groups, Label set, IA hypotheses | RAID Log, Status Report Source | Salience Diagram, Strategy per Class | ROAM Board, Owner List |
Tagsno overlap | Information architectureNavigationStructure | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance | RiskAgileTrackingAlignment |