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)
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Paper illustration of MVP Test Matrix with a method-specific labelled workspace.
Product Discovery
MVP Test Matrix
Paper illustration of a branching tree with an outcome at its root, customer opportunities, solution options and small experiment cards.
Product Discovery
Opportunity Solution Tree
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.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 several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan.When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additionalMehrere Wochen45-75 min1-2 h Setup, laufend
Participantsdifferent
Designers, developers as users, and facilitation2-6 researchers plus sample2-82-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesTest Matrix, Test PlanOpportunity Solution Tree, Experiment Backlog, Learning Log
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
OutcomesInnovationResearchQuantitative
ExperimentsValidationDiscoveryOptions
DiscoveryOutcomesExperimentsOpportunity
Add more methods