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 |  Facilitation Stakeholder Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 20–45 min | 60–90 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Small cross-functional group | 2-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Stakeholder Map, Engagement Plan, Risk Notes | 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 |
Tagsno overlap | RiskDecisionFailurePlanning | StakeholdersAlignmentFacilitationChange | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
