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 | ![]() Operations DMAIC | ![]() UX Research Contextual Inquiry | ![]() Domain Modeling Domain Context Map |
|---|---|---|---|---|
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. | For a process problem with fluctuating performance, the method brings analysis and improvement into a disciplined sequence. It creates a framework in which numbers, causes, and control come together. | 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. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-4 Wochen | 2-12 Wochen | 1-3 Wochen | 1-3 h |
Participantsdifferent | 5-20 | 3-10 | 4-12 Beobachtungen | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Project Charter, Measurement Plan, Cause Analysis, Control Plan | Field Notes, Workflow Insights, Pain Points | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | UX researchTrackingBehavior | Continuous improvementQualityProcess improvement | UX researchObservationContext | Domain-Driven DesignContextBoundaries |



