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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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.Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.
Complexitydifferent
MediumMediumHighHigh
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional2-4 hMehrere Wochen4-5 Tage
Participantsdifferent
Designers, developers as users, and facilitation5-152-6 researchers plus sample5-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsQuality Scenarios, Priority List, Architecture ConcernsDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesPrototype, Test Findings, Decision Rationale
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
RequirementsArchitectureWorkshop
OutcomesInnovationResearchQuantitative
Design sprintPrototypeValidationInnovation
Add more methods