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
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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
HighLowLowMedium
Timedifferent
Mehrere Wochen60-90 min45-90 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-6 researchers plus sample4-122-8Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesAnnotated Diagram, Prioritized Risk List, Action BacklogAssumption List, Critical Assumptions, Learning PlanPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
OutcomesInnovationResearchQuantitative
RiskArchitectureWorkshopValidation
AssumptionsRiskDecisionDiscovery
ArchitectureEngineeringFeedbackValidationTasks
Add more methods