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 |  Engineering Failure Scenario Analysis |  Facilitation Stakeholder Mapping |  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. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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. | 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 | Low | Low |
Timedifferent | 1-4 Wochen | 1-3 h | 60–90 min | 30 min Setup, dann laufend |
Participantsdifferent | 5-20 | 3-8 | 2-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop | Workshop + async | Async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Stakeholder Map, Engagement Plan, Risk Notes | RAID Log, Status Report Source |
Tagsno overlap | UX researchTrackingBehavior | FailureResilienceRisk | StakeholdersAlignmentFacilitationChange | RiskTrackingStakeholdersGovernance |