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 arc42 |  Agile Specification by Example |  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. | 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 | Low | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-2 Tage | 60-90 min pro Feature | 60-120 min |
Participantsdifferent | 4-12 Beobachtungen | 1-4 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Architecture Document, Context View, Runtime View, Deployment View | Example Table, Acceptance Tests | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | UX researchObservationContext | ArchitectureDocumentationCommunication | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas |