View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Force Field AnalysisLASR (Lightweight Approach for Software Reviews)Failure Mode and Effects AnalysisFishbone Diagram
| Criterion |  Decision Making Force Field Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Failure Mode and Effects Analysis |  Operations Fishbone Diagram |
|---|---|---|---|---|
Purposedifferent | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-6 h | 30-60 min |
Participantsdifferent | 3-12 | 1 or a small team; particularly suitable for 3–4 people | 3-10 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Force Field Map, Change Levers, 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 | FMEA Table, Risk Priority, Mitigation Actions | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ChangeDecisionStrategy | ArchitectureQualityRiskAssessmentLean | RiskQualityOperationsRoot cause | Root causeQualityOperations |