View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Reverse BrainstormingLASR (Lightweight Approach for Software Reviews)Failure Mode and Effects Analysis
| Criterion |  Innovation Reverse Brainstorming |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|
Purposedifferent | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. | 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 a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 30-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-6 h |
Participantsdifferent | 3-12 | 1 or a small team; particularly suitable for 3–4 people | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Reverse Ideas, Risk Themes, Solution Ideas | 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 | FMEA Table, Risk Priority, Mitigation Actions |
Tags1 shared | BrainstormingIdeationCreativityRisk | ArchitectureQualityRiskAssessmentLean | RiskQualityOperationsRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
