methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop
Paper illustration for Opportunity Interview
Product Discovery
Opportunity Interview
Paper illustration for Problem Interview
Product Discovery
Problem Interview
Purposedifferent
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.When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities.When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution.
Complexitysame
MediumMediumMedium
Timedifferent
2-4 h30-60 min je Interview30-60 min je Interview
Participantsdifferent
5-155-12 Interviews5-12 Interviews
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Quality Scenarios, Priority List, Architecture ConcernsInterview Notes, Opportunity Themes, Customer QuotesProblem Evidence, Risk Notes, Customer Segments
Tagsno overlap
RequirementsArchitectureWorkshop
DiscoveryInterviewsOpportunityCustomer
DiscoveryInterviewsValidation
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Risk Storming.
Architecture
Risk Storming
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Concierge MVP
Product Discovery
Concierge MVP
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming