View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Diary StudyLASR (Lightweight Approach for Software Reviews)RAID LogFailure Mode and Effects Analysis
| Criterion |  UX Research Diary Study |  Architecture LASR (Lightweight Approach for Software Reviews) |  Delivery RAID Log |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-4 Wochen | 3–4 h for initial assessment; preparation and deeper analysis additional | 30 min Setup, dann laufend | 2-6 h |
Participantsdifferent | 5-20 | 1 or a small team; particularly suitable for 3–4 people | 1-3 maintaining, briefing for everyone | 3-10 |
Formatdifferent | Async | Workshop + async | Async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | RAID Log, Status Report Source | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | UX researchTrackingBehavior | ArchitectureQualityRiskAssessmentLean | RiskTrackingStakeholdersGovernance | RiskQualityOperationsRoot cause |