View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations ABC Analysis | ![]() Domain Modeling Domain Context Map | ![]() UX Research Contextual Inquiry |
|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30-60 min | 1-3 h | 1-3 Wochen |
Participantsdifferent | 1-5 | 3-10 | 4-12 Beobachtungen |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | Domain Context Map, Boundary Notes, Ownership Map | Field Notes, Workflow Insights, Pain Points |
Tagsno overlap | PrioritizationOperationsPortfolio | Domain-Driven DesignContextBoundaries | UX researchObservationContext |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






