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 Contextual Inquiry |  Delivery RAID Log |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
Purposedifferent | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 Wochen | 30 min Setup, dann laufend | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 4-12 Beobachtungen | 1-3 maintaining, briefing for everyone | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | RAID Log, Status Report Source | 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 |
Tagsno overlap | UX researchObservationContext | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
