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 |  UX Research Tree Testing |  Facilitation Stakeholder Salience Model |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
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 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. | 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 | Medium | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 1-2 Tage | 60-90 min | 60–90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Based on research question | 3-6 | 2-8 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Findability Metrics, Path Analysis, Revised IA | Salience Diagram, Strategy per Class | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Information architectureNavigationFindability | StakeholdersFacilitationAlignmentGovernance | StakeholdersAlignmentFacilitationChange |