View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Architecture Decision Record |  Decision Making Pre-Mortem |
|---|---|---|---|
Purposedifferent | 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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 15-45 min | 20–45 min |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 1-3 | Small cross-functional group |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | 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 | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | ArchitectureRationaleDocumentationGovernance | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
