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 Domain Context Map |  Architecture arc42 |  Architecture Architecture Communication 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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 1-2 Tage | 60-120 min |
Participantsdifferent | 4-12 Beobachtungen | 3-10 | 1-4 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Domain Context Map, Boundary Notes, Ownership Map | Architecture Document, Context View, Runtime View, Deployment View | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignContextBoundaries | ArchitectureDocumentationCommunication | ArchitectureCommunicationStakeholdersCanvas |