View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Change Analysis |  Business Strategy Value Chain Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 45-120 min | Half day | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-6 | 3-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Value Chain Map, Lever List | 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 |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | StrategyBusiness modelDiagnosisAnalysis | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
