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 | ![]() Facilitation Team Charter | ![]() Facilitation Stakeholder Salience Model | ![]() Delivery RAID Log |
|---|---|---|---|---|
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. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-4 Wochen | 2-4 h | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 5-20 | 3-12 | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop | Workshop | Async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Team Charter, Working Norms, Role Notes | Salience Diagram, Strategy per Class | RAID Log, Status Report Source |
Tagsno overlap | UX researchTrackingBehavior | TeamAlignmentCollaboration | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |



