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 |  Domain Modeling Domain Context Map |  Operations Kaizen Event |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | 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 tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 0.5-5 Tage | 45-90 min |
Participantsdifferent | 4-12 Beobachtungen | 3-10 | 4-10 | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Domain Context Map, Boundary Notes, Ownership Map | Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignContextBoundaries | LeanContinuous improvementOperations | LeanProblem solvingCoachingOperations |