View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Agile ROAM Board |  UX Research Card Sorting |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 | Low | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 20-45 min | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-15 | Based on research question | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | ROAM Board, Owner List | Content groups, Label set, IA hypotheses | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | Information architectureNavigationStructure | StakeholdersFacilitationAlignmentGovernance |