View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Innovation TRIZ |  Business Strategy Value Chain Analysis |  Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | Medium | High | High | High |
Timedifferent | 30-240 min | 1-4 h | Half day | Half day |
Participantsdifferent | 1-6 | 2-8 | 3-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Contradiction Statement, Inventive Principles, Solution Concepts | Value Chain Map, Lever List | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | InnovationProblem solvingContradictionsCreativity | StrategyBusiness modelDiagnosisAnalysis | StrategyBusiness modelRiskDiagnosis |