View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Product Discovery Context Canvas |  UX Research Contextual Inquiry |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | 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. | 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 | 60-90 min pro Feature | 45-90 min | 1-3 Wochen | 60-120 min |
Participantsdifferent | 3-6 | 3-10 | 4-12 Beobachtungen | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Context canvas, Open questions, Shared context notes | Field Notes, Workflow Insights, Pain Points | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ContextFramingRequirementsCanvas | UX researchObservationContext | ArchitectureCommunicationStakeholdersCanvas |