View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Leverage PointsFailure Mode and Effects AnalysisValue Chain AnalysisSAAM (Software Architecture Analysis Method)
| Criterion |  Systems Thinking Leverage Points |  Operations Failure Mode and Effects Analysis |  Business Strategy Value Chain Analysis |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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. |
Complexitysame | High | High | High | High |
Timedifferent | Half day | 2-6 h | Half day | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-12 | 3-10 | 3-8 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Leverage Map, Action Strategy | FMEA Table, Risk Priority, Mitigation Actions | Value Chain Map, Lever List | 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 |
Tagsno overlap | Systems thinkingChangeStrategy | RiskQualityOperationsRoot cause | StrategyBusiness modelDiagnosisAnalysis | ArchitectureChangeAnalysisComparisonQuality |