methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Contextual Inquiry.
UX Research
Contextual Inquiry
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
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 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.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-3 Wochen1-3 h1-4 h1-3 h
Participantsdifferent
4-12 Beobachtungen3-103-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Field Notes, Workflow Insights, Pain PointsDomain Context Map, Boundary Notes, Ownership MapChallenge Findings, Risk Register, Mitigation PlanContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
UX researchObservationContext
Domain-Driven DesignContextBoundaries
RiskDecisionSensemaking
Domain-Driven DesignBoundariesStrategy
Add more methods