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 EventStorming |  Domain Modeling Domain Context Map |  Innovation Starbursting |
|---|---|---|---|---|
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 consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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. | Helps clarify ideas, open questions, and testable next steps in concrete terms. It opens the thinking space, collects ideas, and leads to testable options. The result is captured as a star-shaped question map, question list, and assumption list. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen | 2-8 h | 1-3 h | 30-60 min |
Participantsdifferent | 4-12 Beobachtungen | 5-12 | 3-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Domain Context Map, Boundary Notes, Ownership Map | Star-Shaped Question Map, Question List, Assumption List |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignEventsDiscoveryWorkshop | Domain-Driven DesignContextBoundaries | BrainstormingIdeationWorkshopDiscovery |