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 Diary Study |  Delivery RAID Log |  Agile Specification by Example |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. | 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 | Medium | Medium |
Timedifferent | 1-4 Wochen | 30 min Setup, dann laufend | 60-90 min pro Feature | 60-90 min |
Participantsdifferent | 5-20 | 1-3 maintaining, briefing for everyone | 3-6 | 3-6 |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | RAID Log, Status Report Source | Example Table, Acceptance Tests | Salience Diagram, Strategy per Class |
Tagsno overlap | UX researchTrackingBehavior | RiskTrackingStakeholdersGovernance | AgileRequirementsExamplesBehavior-Driven Development | StakeholdersFacilitationAlignmentGovernance |