View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Context Canvas |  UX Research Contextual Inquiry |  Architecture Quality Attribute Workshop |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 Wochen | 2-4 h | 60-90 min |
Participantsdifferent | 3-10 | 4-12 Beobachtungen | 5-15 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Context canvas, Open questions, Shared context notes | Field Notes, Workflow Insights, Pain Points | Quality Scenarios, Priority List, Architecture Concerns | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ContextFramingRequirementsCanvas | UX researchObservationContext | RequirementsArchitectureWorkshop | RiskArchitectureWorkshopValidation |