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 |  Operations Root Cause Tree Analysis |  Domain Modeling Domain Context Map |  Operations 5 Whys |
|---|---|---|---|---|
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. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen | 1-3 h | 1-3 h | 15-30 min |
Participantsdifferent | 4-12 Beobachtungen | 2-8 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Cause Tree, Evidence Notes, Countermeasures | Domain Context Map, Boundary Notes, Ownership Map | Root cause notes, Countermeasures |
Tagsno overlap | UX researchObservationContext | Root causeTreeIncidentQuality | Domain-Driven DesignContextBoundaries | Root causeIncidentLeanProblem solving |