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) |  Decision Making Assumption Surfacing |  Decision Making Red Teaming |
|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 | Medium | Low | High |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min | 1-4 h |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
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 | Assumption List, Critical Assumptions, Learning Plan | Challenge Findings, Risk Register, Mitigation Plan |
Tags1 shared | ArchitectureQualityRiskAssessmentLean | AssumptionsRiskDecisionDiscovery | RiskDecisionSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
