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 Context Map |  Business Strategy PESTLE Analysis |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 1-3 h | 1-3 h |
Participantsdifferent | 4-12 Beobachtungen | 2-8 | 2-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Context Map, Integration Patterns, Boundary Notes | PESTLE Map, External Risks, Strategic Questions | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignBoundariesStrategy | StrategyMarketAnalysis | Domain-Driven DesignContextBoundaries |