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
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Surveys method illustration showing its working structure
UX Research
Surveys
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal.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.
Complexitydifferent
HighLowMediumMedium
Timedifferent
Mehrere Wochen1-2 h3-14 Tage2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-6 researchers plus sample3-1050+Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesArchitecture Canvas, Goals, Constraints, Quality AttributesSurvey Results, Charts, Segment InsightsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
OutcomesInnovationResearchQuantitative
CanvasArchitectureAlignmentWorkshop
QuantitativeResearchValidation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods