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 A3 Problem Solving |  Business Strategy Value Chain Analysis |  Engineering Hypothesis-Driven Troubleshooting |
|---|---|---|---|
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. | 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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 45-90 min | Half day | 30-240 min |
Participantsdifferent | 2-5 | 3-8 | 1-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Value Chain Map, Lever List | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | LeanProblem solvingCoachingOperations | StrategyBusiness modelDiagnosisAnalysis | TroubleshootingProblem solvingDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
