View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:GAP AnalysisFishbone DiagramLASR (Lightweight Approach for Software Reviews)Failure Mode and Effects Analysis
| Criterion | ![]() Business Strategy GAP Analysis | ![]() Operations Fishbone Diagram | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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 | Medium | Low | Medium | High |
Timedifferent | 1-3 h | 30-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-6 h |
Participantsdifferent | 2-8 | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Fishbone Diagram, Cause Categories, Investigation Backlog | 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 |
Tagsno overlap | StrategyAnalysisPlanning | Root causeQualityOperations | ArchitectureQualityRiskAssessmentLean | RiskQualityOperationsRoot cause |



