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 Risk Matrix |  Architecture LASR (Lightweight Approach for Software Reviews) |  Decision Making Red Teaming |
|---|---|---|---|
Purposedifferent | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | 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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 30-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-4 h |
Participantsdifferent | 3-10 | 1 or a small team; particularly suitable for 3–4 people | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Risk Matrix, Top Risk List | 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 | Challenge Findings, Risk Register, Mitigation Plan |
Tags1 shared | RiskDecisionPrioritizationAssessment | ArchitectureQualityRiskAssessmentLean | RiskDecisionSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
