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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
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.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.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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
HighMediumLowMedium
Timedifferent
Mehrere Wochen2–4 h review as a planning range; preparation and evaluation additional60-90 min45-60 min
Participantsdifferent
2-6 researchers plus sampleDesigners, developers as users, and facilitation4-122-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsAnnotated Diagram, Prioritized Risk List, Action BacklogAssumption map, Test backlog, Risk ranking
Tagsno overlap
OutcomesInnovationResearchQuantitative
ArchitectureEngineeringFeedbackValidationTasks
RiskArchitectureWorkshopValidation
AssumptionsRiskExperimentsValidation
Add more methods