View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:A3 Problem SolvingSAAM (Software Architecture Analysis Method)LASR (Lightweight Approach for Software Reviews)Failure Mode and Effects Analysis
| Criterion |  Operations A3 Problem Solving |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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 | High | Medium | High |
Timedifferent | 45-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-6 h |
Participantsdifferent | 2-5 | Architecture experts and stakeholders for scenarios and weighting | 1 or a small team; particularly suitable for 3–4 people | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | 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 | LeanProblem solvingCoachingOperations | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskAssessmentLean | RiskQualityOperationsRoot cause |