View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordOutcome-Driven InnovationFailure Mode and Effects AnalysisLASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture Architecture Decision Record |  Product Discovery Outcome-Driven Innovation |  Operations Failure Mode and Effects Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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. |
Complexitydifferent | Low | High | High | Medium |
Timedifferent | 15-45 min | Mehrere Wochen | 2-6 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 1-3 | 2-6 researchers plus sample | 3-10 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | FMEA Table, Risk Priority, Mitigation Actions | 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 |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OutcomesInnovationResearchQuantitative | RiskQualityOperationsRoot cause | ArchitectureQualityRiskAssessmentLean |