View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Contextual InquiryKnowledge MappingLASR (Lightweight Approach for Software Reviews)Failure Mode and Effects Analysis
| Criterion |  UX Research Contextual Inquiry |  Knowledge Modeling Knowledge Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. | 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 | Medium | High |
Timedifferent | 1-3 Wochen | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-6 h |
Participantsdifferent | 4-12 Beobachtungen | 3-12 | 1 or a small team; particularly suitable for 3–4 people | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Knowledge Map, Critical Knowledge Areas, Transfer Plan | 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 | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | UX researchObservationContext | KnowledgeMappingRisk | ArchitectureQualityRiskAssessmentLean | RiskQualityOperationsRoot cause |