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 |  Business Strategy PESTLE Analysis |  Domain Modeling Context Map |  Business Strategy SWOT Analysis |
|---|---|---|---|---|
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. | 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 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. | SWOT Analysis arranges strengths, weaknesses, opportunities, and threats into a compact picture of the situation. It keeps internal capabilities and external influences separate before strategic options emerge from them. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen | 1-3 h | 1-3 h | 30-60 min |
Participantsdifferent | 4-12 Beobachtungen | 2-10 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | PESTLE Map, External Risks, Strategic Questions | Context Map, Integration Patterns, Boundary Notes | SWOT matrix, Strategic options, Action list |
Tagsno overlap | UX researchObservationContext | StrategyMarketAnalysis | Domain-Driven DesignBoundariesStrategy | StrategyAnalysisMarketPositioning |