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)
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
HighMediumLowLow
Timedifferent
Mehrere Wochen3–4 h for initial assessment; preparation and deeper analysis additional30 min Setup, dann laufend15-45 min
Participantsdifferent
2-6 researchers plus sample1 or a small team; particularly suitable for 3–4 people1-3 maintaining, briefing for everyone1-3
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
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 checksRAID Log, Status Report SourceADR File, Decision Log, Rationale
Tagsno overlap
OutcomesInnovationResearchQuantitative
ArchitectureQualityRiskAssessmentLean
RiskTrackingStakeholdersGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods