View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Jobs to Be DoneLASR (Lightweight Approach for Software Reviews)Architecture Decision Record
| Criterion |  Product Discovery Jobs to Be Done |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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. | 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 | Medium | Medium | Low |
Timedifferent | 1-3 Wochen | 3–4 h for initial assessment; preparation and deeper analysis additional | 15-45 min |
Participantsdifferent | 5-12 Interviews | 1 or a small team; particularly suitable for 3–4 people | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | 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 | ADR File, Decision Log, Rationale |
Tagsno overlap | CustomerOutcomesNeeds | ArchitectureQualityRiskAssessmentLean | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
