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 |  Architecture Request for Comments |  Domain Modeling Domain Context Map |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-3 h |
Participantsdifferent | 4-12 Beobachtungen | 3-20 Reviewer | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Domain Context Map, Boundary Notes, Ownership Map | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | UX researchObservationContext | ArchitectureDecisionAsyncGovernance | Domain-Driven DesignContextBoundaries | Domain-Driven DesignBoundariesModeling |