View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Outcome-Driven InnovationArchitecture Decision RecordLASR (Lightweight Approach for Software Reviews)arc42
| Criterion | ![]() Product Discovery Outcome-Driven Innovation | ![]() Architecture Architecture Decision Record | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Architecture arc42 |
|---|---|---|---|---|
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. | 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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Mehrere Wochen | 15-45 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-2 Tage |
Participantsdifferent | 2-6 researchers plus sample | 1-3 | 1 or a small team; particularly suitable for 3–4 people | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | ADR File, Decision Log, Rationale | Lean 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 checks | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureRationaleDocumentationGovernance | ArchitectureQualityRiskAssessmentLean | ArchitectureDocumentationCommunication |



