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) |  Business Strategy GAP Analysis |  Product Discovery Assumption Mapping |
|---|---|---|---|
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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-3 h | 45-60 min |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
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 | Gap Matrix, Action Plan, Risk Notes | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | StrategyAnalysisPlanning | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
