View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Pre-Mortem |  Architecture LASR (Lightweight Approach for Software Reviews) |  Decision Making Force Field Analysis |
|---|---|---|---|
Purposedifferent | 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. | 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 change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 20–45 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min |
Participantsdifferent | Small cross-functional group | 1 or a small team; particularly suitable for 3–4 people | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Risk list, Mitigation plan, Assumption log | 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 | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | RiskDecisionFailurePlanning | ArchitectureQualityRiskAssessmentLean | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
