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
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration for Argument Mapping
Decision Making
Argument 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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitydifferent
HighMediumHighMedium
Timedifferent
Mehrere Wochen3–4 h for initial assessment; preparation and deeper analysis additional1-4 h1-3 h
Participantsdifferent
2-6 researchers plus sample1 or a small team; particularly suitable for 3–4 people3-81-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksChallenge Findings, Risk Register, Mitigation PlanArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
OutcomesInnovationResearchQuantitative
ArchitectureQualityRiskAssessmentLean
RiskDecisionSensemaking
SensemakingDecisionRationale
Add more methods