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 | ![]() Agile Bucket System |
|---|---|---|---|
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. | When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 30-90 min |
Participantsdifferent | 4-12 Beobachtungen | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Domain Context Map, Boundary Notes, Ownership Map | Bucketed Backlog, Relative Estimates, Split Candidates |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignContextBoundaries | EstimationBacklogRelative sizing |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






