View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy Impact Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Decision Making Pre-Mortem |
|---|---|---|---|
Purposedifferent | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. | 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 | Medium | Low |
Timedifferent | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 20–45 min |
Participantsdifferent | 3-8 | 1 or a small team; particularly suitable for 3–4 people | Small cross-functional group |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Impact Map, Outcome Hypotheses, Delivery Options | 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 | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | OutcomesStrategyBehaviorPlanning | ArchitectureQualityRiskAssessmentLean | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
